This should be a pretty easy issue to reproduce, at least it seems to happen to me very often. (gluster-3.2.5)
After storage backend(s) have been rebooted, the client mounts are often broken until you unmount and remount. Example from this morning: I had rebooted storage servers to upgrade them to ubuntu 12.04. Now at the client side: $ ls /gluster/scratch ls: cannot access /gluster/scratch: Transport endpoint is not connected $ ls /gluster/scratch3 dbbuild DBS $ sudo umount /gluster/scratch $ sudo mount /gluster/scratch $ ls /gluster/scratch dbbuild $ Note that /gluster/scratch is a distributed volume (spread across servers 'storage2' and 'storage3'), whereas /gluster/scratch3 is a single brick (server 'storage3' only). So *some* of the mounts do seem to automatically reconnect - not all are affected. But in future, I think it would be good if the FUSE client could automatically attempt to reconnect under whatever circumstance causes 'Transport endpoint is not connected'; clearly it *can* reconnect if forced. Thanks, Brian. _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
