This was not working for me with the following versions: SSHFS version 2.5 FUSE library version: 2.9.2 fusermount version: 2.9.2 using FUSE kernel interface version 7.19
The following command (nor any permutation of the '-o' options) gives: user@client$ sshfs -o transform_symlinks -o follow_symlinks 192.168.0.16:/storage Shares/timmy-storage/ 192.168.0.16:/storage: Not a directory /storage on 192.168.0.16 is a symlink to /var/run/usbmount/Seagate_Expansion_1, which is itself a symlink (managed by usbmount) which points to /media/usb1. This double symlink might be the cause of the problem, but it's the only way to ensure that the correct USB drive is always mounted in /storage. Since I have control over the server, I eventually gave up on trying to get sshfs to work with symlinks, and just used "mount --bind" on the server instead of a symlink. root@timmy# rm /storage root@timmy# mkdir /storage root@timmy# mount --bind /var/run/usbmount/Seagate_Expansion_1 /storage user@client$ sshfs 192.168.0.16:/storage Shares/timmy-storage/ user@client$ ls -l Shares/timmy-storage total 72 drwxr-xr-x 1 1002 1003 4096 Sep 17 13:58 apps drwxr-xr-x 1 root root 4096 Aug 24 09:15 backup --snip-- You can add 'bind' mounting to fstab (see http://serverfault.com/questions/613179/how-do-i-do-mount-bind-in-etc- fstab). For me that wasn't an option since the 'Seagate_Expansion_1' symlink is not available when 'mount -a' runs at bootup. I had to modify the /etc/usbmount/mount.d/00_create_model_symlink to call mount. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/137875 Title: symbolic links on remote disk do not work in sshfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/137875/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
