sshfs mount option, 'nonempty', causing mount/connection fails: "No such file or directory". still a valid option?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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_read=65536,compression=yes,auto_cache,no_check_root,kernel_cache,workaround=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?



[Index of Archives]     [Linux Filesystem Development]     [Linux Ext4]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux