Bug 1227646

Summary:	Glusterd fails to start after volume restore, tier attach and node reboot
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	asengupt, ashah, asrivast, bugs, byarlaga, gluster-bugs, storage-qa-internal
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1224175
Clones:	1228592 (view as bug list)		Environment:
Last Closed:	2016-06-16 13:07:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1224175
Bug Blocks:	1223636, 1228592

Comment 1 Anand Avati 2015-06-03 10:01:17 UTC

REVIEW: http://review.gluster.org/11060 (snapshot: Fix finding brick mount path logic) posted (#1) for review on master by Avra Sengupta (asengupt)

Comment 2 Anand Avati 2015-06-05 09:22:34 UTC

COMMIT: http://review.gluster.org/11060 committed in master by Krishnan Parthasarathi (kparthas) 
------
commit bf3a6dcdf3c8a8a64e7c864b56c4d9be60fca8e6
Author: Avra Sengupta <asengupt>
Date:   Wed Jun 3 15:18:08 2015 +0530

    snapshot: Fix finding brick mount path logic
    
    Previously while finding brick mount paths
    of snap volume's bricks, we were taking brick order
    into consideration. This logic fails when a brick is
    removed or a tier is added.
    
    Hence modifying the logic to look for the first
    occurence of the word "brick" in the brick path.
    From there we iterate till we find a '/'. The string
    till the first '/' after we encounter the word brick
    is the brick mount path.
    
    Change-Id: Ic85983c4e975e701cdfd4e13f8e276ac391a3e49
    BUG: 1227646
    Signed-off-by: Avra Sengupta <asengupt>
    Reviewed-on: http://review.gluster.org/11060
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Rajesh Joseph <rjoseph>
    Reviewed-by: Krishnan Parthasarathi <kparthas>

Comment 3 Nagaprasad Sathyanarayana 2015-10-25 14:42:12 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 4 Niels de Vos 2016-06-16 13:07:33 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user