Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to mount any remote filesystem using sshfs #39

Closed
Shellcat-Zero opened this issue Jan 3, 2017 · 3 comments
Closed

Unable to mount any remote filesystem using sshfs #39

Shellcat-Zero opened this issue Jan 3, 2017 · 3 comments
Assignees

Comments

@Shellcat-Zero
Copy link

I upgraded libc6 on a stock Ubuntu 14.04 server to Xenial (16.04), which caused sshfs to stop being able to mount anything. I reverted all packages back to trusty-updates, but the problem persists. I appear to have replicated the bug reported at http:https://unix.stackexchange.com/questions/299730/unable-to-mount-any-remote-filesystem-using-sshfs.

The version of sshfs was 2.5.1. I uninstalled and then installed the latest version from this Github repo, to no avail.

sshfs --version
SSHFS version 2.8
FUSE library version: 2.9.2
fusermount version: 2.9.2
using FUSE kernel interface version 7.19

Before mounting (as normal user):

ls -lh
drwxrwxr-x  2 user user 4.0K Dec 25 00:10 mnt/

Then attempting to mount:

sshfs [email protected]:/media/drive /home/user/mnt
fusermount: failed to access mountpoint /home/user/mnt: Permission denied

ls -lh
ls: cannot access mnt: Transport endpoint is not connected
d?????????  ? ?          ?             ?            ? mnt/

The messed up directory can then only be remedied by issuing sudo fusermount -u mnt (root is requred to fix it).

If the drive is attempted by root, I get the message:

mount:  according to mtab, [site] is already mounted on [mountpoint]

It does not appear to be present in /etc/mtab, here is my /etc/mtab:

/dev/sda1 /boot/efi vfat rw,noatime,umask=0077 0 0
/dev/sda4 /home ext4 rw,noatime 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,noexec,nosuid,nodev 0 0
none /sys/fs/cgroup tmpfs rw,uid=0,gid=0,mode=0755,size=1024 0 0
systemd /sys/fs/cgroup/systemd cgroup rw,noexec,nosuid,nodev,none,name=systemd 0 0

I have also noticed this bug triggered after attempting the sshfs mount:

df -lh
df: ‘/run/user/1000/gvfs’: Transport endpoint is not connected
...

Invoking sshfs with '-o sshfs_debug' simply prints the version number, and no further useful information.
On a system with a working sshfs, I can see fuse entries in the mtab, like a gvfsd-fuse entry listing the username, and successfully mounting the drive will show it in the mtab as well. I've reinstalled sshfs and all of its dependencies several times. I've been wrestling with this issue for days, assistance would be appreciated.

@Nikratio
Copy link
Contributor

Nikratio commented Jun 3, 2017

Are you still having this problem? If so, please post the output of:

cat /proc/mounts
ls -l <your-mountpoint>
sshfs <other-opts> <your-mountpoint>

@Nikratio Nikratio self-assigned this Jun 3, 2017
@Shellcat-Zero
Copy link
Author

@Nikratio I had no choice but to reinstall 16.04 from scratch to fix this issue. I suspect some dependency, or version thereof, was not well accounted for, but otherwise I do not know the cause of the problem.

@Nikratio
Copy link
Contributor

Alright, closing this bug then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants