sshfs in 12.04 doesn't like to mount to remote symlinks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sshfs-fuse (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Hi,
In Lucid (sshfs 2.2-1build1) I could sshfs to a symlink on another machine and all was good.
But in Precise (sshfs 2.3-1) it doesn't like to do that unless I pass "-o follow_symlinks".
for example:
on the remote lucid box there is a drive connected to /mnt/data, which is then symlinked to /data.
from another lucid box I can run
sshfs -o idmap=user remote_lucid:/data ~/mnt/lucid_data
but if I try the same from a new Precise box it becomes unhappy:
~/mnt$ ls -l
ls: cannot access lucid_data: Input/output error
total 0
d????????? ? ? ? ? ? lucid_data
changing to add `-o follow_symlinks`:
sshfs -o idmap=user,
it works again. (but all symlinks within the data drive are expanded, which is unideal)
changing to avoid a remote symlink as the source point:
sshfs -o idmap=user remote_
also works, and remote symlinks within there come through ok. It just means I have to
audit a bunch of scripts on a bunch of boxes to make sure everything uses the non-
generalized path for things.
is this new restriction intended behaviour or a regression which snuck in?
thanks,
Hamish
I believe you have to add a trailing slash to the remote path to avoid this bug, like so:
sshfs -o idmap=user remote_lucid:/data/ ~/mnt/lucid_data
See this discussion from a year ago: http:// thread. gmane.org/ gmane.comp. file-systems. fuse.sshfs/ 1182/focus= 1189
Why this bug made it into Ubuntu 12.04 I have no idea.