Hide Forgot
Gluster 3.0.5-1 > > i use glusterfs on debian squeeze. > > i have 2 server with the glusterfs server running (replicate), and a > mount with glusterfs client. > > i have glusterfs-server that use /srv/glusterfs for export > directory. > > i made a mistake to mount the client on the same directory in the > server of one of the glusterfs-server. > > glusterfs -f /etc/glusters/myfs /srv/glusterfs. > > my glusterfs freeze. > > bst regards.
Glusterfs program cannot control whether the mount point is valid or not.
True, but Gluster can send an error instead of just crashing. We don't need recursive mounts to work, we just want a meaningful error message and Gluster not to crash.
(In reply to comment #2) > True, but Gluster can send an error instead of just crashing. We don't need > recursive mounts to work, we just want a meaningful error message and Gluster > not to crash. Gluster is not crashing in this case. It freezes. It is hard to detect, actually almost impossible to detect, if the same directory which is about to be mounted upon, also happens to be the export directory (or its parent directory, or its sub-directory - it would have frozen in those cases as well) of the same volume. Or in a more complicated setup, volume A's mount being volume B's export and volume B's mount being volume A's export (or more such hops). Avati
*** Bug 2495 has been marked as a duplicate of this bug. ***
Planing to keep 3.4.x branch as "internal enhancements" release without any features. So moving these bugs to 3.4.0 target milestone.
CHANGE: http://review.gluster.com/314 (Adding check_recursive_mount() in mount.glusterfs.in) merged in master by Anand Avati (avati)