On Fri, 2020-09-11 at 19:02 -0700, PGNet Dev wrote: > fyi, > > here, on Fedora32 > > rpm -qa | grep ^fuse | sort > fuse-2.9.9-9.fc32.x86_64 > fuse3-3.9.1-1.fc32.x86_64 > fuse3-libs-3.9.1-1.fc32.x86_64 > fuse-common-3.9.1-1.fc32.x86_64 > fuse-libs-2.9.9-9.fc32.x86_64 > fuse-sshfs-3.7.0-3.fc32.x86_64 > > > man mount.fuse > ... > nonempty > Allows mounts over a non-empty file or directory. By > default these mounts are rejected to prevent accidental covering up > of data, which could for example prevent automatic backup. > ... > > reading > > [SOLVED] cannot mount sshfs with "nonempty" option > https://bbs.archlinux.org/viewtopic.php?id=228225 > > "The "nonempty" option has been removed from libfuse > since version 3.0.0 to bring fuse "in-line with the behavior of the > regular mount command". > > In version 2.9-1 the sshfs binary links against libfuse > 2.9.7, the new version links against libfuse 3.1.0." > > ... > > "TL;DR: You can just remove the nonempty mount option, > it is the default behaviour now." > > > iiuc, looks like > > (1) the Fedora man needs updating It does, yes. > (2) the 'nonempty' option is deprecated, and is functionally the > default > > perhaps a more informative error is called for? may be too far gone > ... For autofs that improved error message needs to come from the mount, which I think should be calling mount.fuse, which should know full well to issue a warning and ignore it. Ian
