Hide Forgot
started volume using gluster commands.During glusterfs mount ,it didn't produce any errors ,when wrong servername & volume-name is used. mount shows as mounted while df hangs. # mount -t glusterfs server1000:xyz /home/test/ # mount glusterfs#client.vol on /opt type fuse (rw,allow_other,default_permissions,max_read=131072) glusterfs#server1 on /mnt type fuse (rw,allow_other,default_permissions,max_read=131072) glusterfs#server1000 on /home/test type fuse (rw,allow_other,default_permissions,max_read=131072) #ps aux | grep glusterfs ps aux | grep glu root 24004 0.0 0.1 62044 8792 ? Ssl 00:53 0:00 /usr/local/sbin/glusterfs --log-level=NORMAL --volfile-id=test-volume --volfile-server=server1 /mnt root 24039 0.0 0.0 76004 868 pts/2 S+ 00:53 0:00 mount -t glusterfs server1:test-volume /mnt root 24040 0.0 0.0 65912 1248 pts/2 S+ 00:53 0:00 /bin/bash /sbin/mount.glusterfs server1:test-volume /mnt -o rw root 24194 0.0 0.1 62044 8792 ? Ssl 00:55 0:00 /usr/local/sbin/glusterfs --log-level=NORMAL --volfile-id=xyz --volfile-server=server1000 /home/test/
Can you check with later releases? At least it should not hang for ever with 3.1qa40+
*** Bug 2038 has been marked as a duplicate of this bug. ***
PATCH: http://patches.gluster.com/patch/5990 in master (glusterfsd-mgmt: handle the RPC_DISCONNECT event properly)
Checked in 3.2.x release.