Bug 763185 (GLUSTER-1453)

Summary: mount command didn't give error message
Product: [Community] GlusterFS Reporter: Lakshmipathi G <lakshmipathi>
Component: fuseAssignee: Amar Tumballi <amarts>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 3.1-alphaCC: amarts, anush, gluster-bugs, jacob, vijay, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: RTA Mount Type: fuse
Documentation: --- CRM:
Verified Versions: 3.2.5 Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lakshmipathi G 2010-08-27 08:06:56 UTC 
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/
Comment 1 Amar Tumballi 2010-10-05 07:24:32 UTC 
Can you check with later releases? At least it should not hang for ever with 3.1qa40+
Comment 2 Amar Tumballi 2011-01-20 07:17:19 UTC 
*** Bug 2038 has been marked as a duplicate of this bug. ***
Comment 3 Anand Avati 2011-01-27 17:17:53 UTC 
PATCH: http://patches.gluster.com/patch/5990 in master (glusterfsd-mgmt: handle the RPC_DISCONNECT event properly)
Comment 4 Anush Shetty 2011-12-08 06:43:33 UTC 
Checked in 3.2.x release.