I am using glusterfs on several Ubuntu servers: two of them are running glusterfs servers in replication mode.
Without any clear error, the glusterfs partition became stale and the system shows this error when I try to access the stale partition:
Transport endpoint is not connected
Also, when running ls -l
on the parent folder I get:
d????????? ? ? ? ? ? myfolder
I tried all types of commands that I can find to umount this partition, but I could not get it done:
umount -l /path/to/mount/point
umount -f /path/to/mount/point
Also, using fuser
command to show processes accessing this folder did not work. Unload the fuse kernel module can not be done as it is clear from the kernel config that fuse is built into the kernel and not a loadable module. I found this line in /boot/config-2.6.32-24-server
CONFIG_FUSE_FS=y
I have been left with two options:
- Reboot the system.
- Create another mount point like myfolder2 and mount this again using
sudo glusterfs -f /etc/glustefs/glusterfs.vol /path/to/folder2
.
Of course, I have chosen to go with option 2.
Anyone faced such an issue before?
Anyone has a better solution for such a case?
Try stopping the glusterfs service, first on the second node, then on the first node. For Ubuntu, the command is:
Alternatively, remove the glusterfs service from startup on both machines and reboot both. The partitions shouldn't mount on boot then, as glusterfs does this job.
This works to resolve the 'Transport endpoint is not connected' error with gluster