I needed to locally edit remote files on my server, so I tried to mount the whole remote file system (/
) on my local system with SSHFS like so:
$ sshfs [email protected]:// /mnt -p 22
Then it stuck (cursor blinking, no output), so obviously I cancelled it with Ctrl+C.
After that, the mount point folder /mnt
became sort of unusable, unreachable (you name it) and kept returning me this error message on any attempt to access it:
fuse: bad mount point `/mnt': Transport endpoint is not connected
And it took this weird look in its parent folder:
$ ls -l /
...
d????????? ? ? ? ? ? mnt`
...
1. Kill all
sshfs
processesEither with
killall
command:or selectively:
Find all running
sshfs
processes:Say you've got two of them running:
Now kill them both or selectively by identifying them by their PID:
2. Unmount your mount point
3. Edit
/etc/fuse.conf
so you never meet thefuse: bad mount point `/mnt': Transport endpoint is not connected
error again:Open it as root with your favorite editor, for example
user_allow_other
line.4. Use SSHFS with the following options:
-d
turns debug mode on (gives more output)-o
stands for "option"-p
allows you to specify port number-C
turns on compressionSources: