Vehicle endpoint not connected

FUSE constantly (every 2 to 3 days) gives me this Transport endpoint is not connected error on my mount point, and the only thing that seems to fix it is a reboot.

I currently have mount point settings, I'm not sure what other details I should add here, so let me know if I missed something.

 /dev/sdc1 /mnt/hdd2 ext4 defaults 0 0 /dev/sdb1 /mnt/hdd1 ext4 defaults 0 0 mhddfs#/mnt/hdd1,/mnt/hdd2 /data fuse defaults,allow_other 0 0 
+57
mount fuse
Jul 26 '14 at 1:37
source share
4 answers

There is a problem with segmentation that was introduced in 0.1.39. You can check out my repository that fixed this: https://github.com/vdudouyt/mhddfs-nosegfault

+2
May 05 '15 at 6:49
source share

I have exactly the same problem. I did not find a solution anywhere, but I was able to fix it without rebooting by simply disconnecting and remounting the mount point.

For your system, the commands will be as follows:

 fusermount -uz /data mount /data 

-z forces disconnect, which decided to restart for me. You may need to do this as sudo depending on your installation. You may encounter the error below if the command does not have the required elevated permissions:

fusermount: record for / data not found in / etc / mtab

I am using Ubuntu 14.04 LTS with the current version of mhddfs .

+111
Sep 23 '14 at 2:57
source share

This is usually caused by the fact that the mount directory remains set due to a failure of your file system. Go to the parent directory of the mount point and enter fusermount -u YOUR_MNT_DIR .

If this does not do the trick, do sudo umount -l YOUR_MNT_DIR .

+44
Apr 01 '15 at 20:59 on
source share

I get this error from the sshfs command from Linux from Linux to debian linux on Mindstorms EV3 brick over a local network and over a wireless connection.

Bash command:

 el@defiant /mnt $ sshfs root@192.168.13.102:/root -p 22 /mnt/ev3 fuse: bad mount point `/mnt/ev3': Transport endpoint is not connected 

This is fixed with the following command and try again:

 fusermount -u /mnt/ev3 

These additional sshfs options prevent the above error from matching:

 sudo sshfs -d -o allow_other -o reconnect -o ServerAliveInterval=15 root@myremoteserver.com:/var/lib/redmine/plugins /mnt -p 12345 -C 

To use allow_other above, you need to uncomment the last line in /etc/fuse.conf :

 # Set the maximum number of FUSE mounts allowed to non-root users. # The default is 1000. # #mount_max = 1000 # Allow non-root users to specify the 'allow_other' or 'allow_root' # mount options. # user_allow_other 

Source: http://slopjong.de/2013/04/26/sshfs-transport-endpoint-is-not-connected/

+12
Jul 18 '15 at 17:39
source share



All Articles