Hi! Thanks for the patch! The version parsing logic looks a little scary to me, I tried to have a simpler solution. Can you try6eee5f2 and see if it fixes your problem?

Also, gocryptfs will keep the-nonempty option, as I think it is useful. Mounting over non-empty directories should still be rejected by default, also on libfuse3.

Hi! Thanks for the patch! The version parsing logic looks a little scary to me, I tried to have a simpler solution. Can you try6eee5f2 and see if it fixes your problem?

Also, gocryptfs will keep the-nonempty option, as I think it is useful. Mounting over non-empty directories should still be rejected by default, also on libfuse3.

Mounting over non-empty directoriesis allowed by default in libfuse 3.0 to match the behavior of mount.

There is a changelog entry for libfuse3.0 that explains why the -nonempty option breaks with libfuse3.
http://fuse.996288.n3.nabble.com/ANNOUNCE-libfuse-3-0-0-has-been-released-td14403.html

The-o nonempty mount point has been removed, mounting over
non-empty directories is now always allowed. This brings the
behavior of FUSE file systems in-line with the behavior of the
regularmount command.

File systems that do not want to allow mounting to non-empty
directories should perform this check themselves before handing
control to libfuse.
Here is the error I get with this commit:

Password: Decrypting master key/usr/bin/fusermount: unknown option 'nonempty'fuse.NewServer failed: fusermount exited with code 256

This is on Ubuntu 20.04. I am happy to keep testing for you until we get this right. My PR worked, but I do agree that I wasn't real happy with the version checking and was hoping you knew a better way.

I did not copy the binary built from6eee5f2 to /usr/bin/gocryptfs. After I did this it works and I am happy with it. Thanks for accepting part of my patch and help!

Thanks for testing! Merged to master.

Mounting over non-empty directories should still be rejected by default, also on libfuse3.

Sorry, that was unclear! gocryptfs will keep rejecting nonempty directories per default, also when using libfuse3. This is checked inside gocryptfs by theisEmptyDir() function and does not depend on libfuse behavoir.

Mounting over non-empty directories should still be rejected by default, also on libfuse3.

Sorry, that was unclear! gocryptfs will keep rejecting nonempty directories per default, also when using libfuse3. This is checked inside gocryptfs by theisEmptyDir() function and does not depend on libfuse behavoir.
Yea, that wording threw me off for a bit and made me re-explain, but I eventually knew what you meant. Will I get a little credit in the git log or anywhere?