Bug 1044797 - mount option "backupvolfile-server" causes mount to fail with "Invalid argument"
Summary: mount option "backupvolfile-server" causes mount to fail with "Invalid argument"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glusterfs
Version: 6.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1023950 1044799
Blocks: 1039643 1052381
TreeView+ depends on / blocked
 
Reported: 2013-12-19 03:19 UTC by Vivek Agarwal
Modified: 2016-02-18 00:03 UTC (History)
18 users (show)

Fixed In Version: glusterfs-3.4.0.57rhs
Doc Type: Bug Fix
Doc Text:
When trying to mount a remote gluster share using the "backupvolfile-server" option, the process failed and returned an "Invalid argument" error message. A new mount point option, backup-volfile-servers, has been added to provide backward compatibility and allows remote gluster shares to be mounted successfully.
Clone Of: 1023950
Environment:
Last Closed: 2014-10-14 08:07:02 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1576 0 normal SHIPPED_LIVE glusterfs bug fix and enhancement update 2014-10-14 01:27:26 UTC

Comment 1 Vivek Agarwal 2014-01-13 17:32:58 UTC 
Build done for 6.6, awaiting ack for 6.5z to make the build on 6.5
Comment 6 SATHEESARAN 2014-09-22 05:17:17 UTC 
Verified with the glusterfs native client - glusterfs-3.6.0.29-2.el6

'backupvolfile-server' option is available with this native client, and thus enabling backward compatibility.
Comment 8 errata-xmlrpc 2014-10-14 08:07:02 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1576.html
Note You need to log in before you can comment on or make changes to this bug.