Bug 764817 (GLUSTER-3085)

Summary:	backupvolfile-server option doesn't work
Product:	[Community] GlusterFS	Reporter:	Jeff Darcy <jdarcy>
Component:	scripts	Assignee:	Amar Tumballi <amarts>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	mainline	CC:	gluster-bugs, vraman
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jeff Darcy 2011-06-24 17:25:11 UTC

The code to check the exit code from glusterfs gets one that only indicates glusterfs was able to fork, not that the mount actually succeeded.  Therefore, the code to use backupvolfile_server would never get called.  I'll send a patch as soon as I get a number for this bug.

Comment 1 Amar Tumballi 2011-06-27 03:02:12 UTC

Hi Jeff, 

bug 762935 is open for handling this issue. With current requirement of 'glusterd' for getting volume file, getting remote-port etc, there was some issues with it.

Will have a chat here locally, and update on our take on properly returning the status of gluster process.

Regards,
Amar

Comment 2 Amar Tumballi 2011-07-05 01:39:05 UTC

The issue here is actually the return value is 0 even in case of failures. Marking duplicate of bug 762935

*** This bug has been marked as a duplicate of bug 1203 ***

Comment 3 Anand Avati 2011-07-12 09:37:44 UTC

PATCH: http://patches.gluster.com/patch/7796 in master (mount.glusterfs: fix to handle the error cases better)