Bug 796101

Summary: mount.glusterfs returns error when mount succeeds
Product: [Community] GlusterFS Reporter: Anush Shetty <ashetty>
Component: fuseAssignee: Amar Tumballi <amarts>
Status: CLOSED UPSTREAM QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: amarts, gluster-bugs, vraman
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-27 07:34:03 UTC Type: ---
Regression: --- Mount Type: fuse
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Anush Shetty 2012-02-22 10:15:45 UTC 
Description of problem: 
How reproducible: When primary volfile-server was incorrect but backupvolfile-server had the proper volfile-server name, the mount succeeded but still the mount command returned error.



Version-Release number of selected component (if applicable): 3.3.0qa23


Steps to Reproduce:
1. mount -t glusterfs -o backupvolfile-server=shortwing 192.168.2.123:/test2 /falcon/mnt
2.
3.
  
Actual results:

# mount -t glusterfs -o backupvolfile-server=shortwing 192.168.2.123:/test2 /falcon/mnt
Mount failed. Please check the log file for more details.

# df -h &
[1] 25347
root@shortwing:~# Filesystem            Size  Used Avail Use% Mounted on
192.168.2.123:/test2  191G  217M  191G   1% /falcon/mnt



Expected results: It shouldn't given an error message.
Comment 1 Anand Avati 2012-02-22 12:18:01 UTC 
CHANGE: http://review.gluster.com/2798 (mount.glusterfs: multiple fixes) merged in master by Vijay Bellur (vijay)
Comment 2 Anush Shetty 2012-02-27 07:33:44 UTC 
Verfied in 3.3.0qa24. This issue is fixed now.