On Fri, 2020-09-11 at 16:47 -0700, PGNet Dev wrote: > i'm setting up auto.sshfs, provided by > > rpm -qa | grep ^autofs > autofs-5.1.6-7.fc32.x86_64 > > on a new server > > grep PRETTY /etc/os-release > PRETTY_NAME="Fedora 32 (Server Edition)" > > > my (usual) config, in-place on all my prior/other-OS boxes, includes > > cat /etc/auto.master > /mnt/nfs4 /etc/auto.nfs4 --timeout=10,--ghost > /mnt/sshfs /etc/auto.sshfs --timeout=30,--ghost > > where mounts are typically, > > cat /etc/auto.sshfs > > example - > fstype=fuse,rw,nodev,nonempty,allow_other,reconnect,uid=0,gid=0,max_r > ead=65536,compression=yes,auto_cache,no_check_root,kernel_cache,worka > round=rename,ssh_command="/usr/bin/ssh -F > /usr/local/etc/ssh/ssh_config" :sshfs\#root@xxxxxxxxxxxxxxxx\:/ > > with that^, > > cd /mnt/sshfs/example > > works exactly as expected -- on all _except_ these new Fedora > installs > > here, > > cd /mnt/sshfs/example > > returns > > ls: cannot access 'sshfs/example/': No such file or directory > > simply removing 'nonemmpty' > > - example -fstype=fuse,rw,nodev,nonempty,allow_other,... > + example -fstype=fuse,rw,nodev,allow_other,... > > cures the problem. > > is 'nonempty' still valid usage with autofs sshfs mounts? > is additional/difference config req'd on Fedora, or perhaps more > recent autofs? The autofs on f33 should be close to what's in the upstream repo., that's the latest release plus patches that have been pushed to the repo., so there isn't a more recent autofs. This could be a bug I've introduced or perhaps a change to what's used to mount these. How about you get a debug log so we can check. Set "logging = debug" in /etc/autofs.conf and use journalctl to collect the log output, like "journalctl -f | tee autofs.log". Obviously you can grep for automount and perhaps edit the log a little to get rid of anything that might not be appropriate for a public mailing list or send it to me privately. Ian
