You are not logged in.
I recently updated my system for the first time in 2 months and noticed that all of my sshfs shares stopped mounting. Attempting to mount them via
# mount -a
would result in
fuse: unknown option(s): `-o cache=no'
The sshfs man page still shows the option in the list:
-o cache=BOOL
enable caching {yes,no} (default: yes)
Full /etc/fstab entry for one of the shares:
myuser@192.168.1.2:/mnt/data/share /home/myuser/Share fuse.sshfs x-systemd.automount,idmap=user,port=12345,_netdev,identityfile=/home/myuser/.ssh/id_rsa,allow_other,default_permissions,uid=1000,gid=1005,reconnect,cache=no,kernel_cache,compression=no 0 0
I might be missing something obvious here, but removing the "cache=no" part from my /etc/fstab does allow me to mount the shares. If you want to know why I'm using this option in the first place, see here.
Any ideas?
Last edited by Soukyuu (2017-08-07 08:20:36)
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
sshfs has switched to the new fuse 3 API, so maybe that parameter was obsoleted there?
Offline
If that is the case, shouldn't it have been removed from the man page? I guess I should poke the devs @github...
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Well, it turns out the option was renamed in 3.0, but the man page was not edited accordingly. Also, from sshfs 3.1 onwards the legacy option is also silently accepted again. So I'm marking this as solved
[ Arch x86_64 | linux | Framework 13 | AMD Ryzen™ 5 7640U | 32GB RAM | KDE Plasma Wayland ]
Offline
Thanks for working this out, I stumbled upon the same thing today.
For everybody arriving here via their favourite Internet search engine: the renamed option name is '-o dir_cache'
Offline