Bug 1229331

Summary:	Disperse volume : glusterfs crashed
Product:	[Community] GlusterFS	Reporter:	Pranith Kumar K <pkarampu>
Component:	disperse	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	3.7.0	CC:	amukherj, aspandey, bugs, byarlaga, gluster-bugs, pkarampu, rhs-bugs, rkavunga, sdharane
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1228952	Environment:
Last Closed:	2015-06-20 09:50:18 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:	1228529, 1228952
Bug Blocks:	1223636

Comment 1 Anand Avati 2015-06-08 13:31:25 UTC

REVIEW: http://review.gluster.org/11128 (cluster/ec: Prevent double unwind) posted (#1) for review on release-3.7 by Pranith Kumar Karampuri (pkarampu)

Comment 2 Anand Avati 2015-06-18 12:47:39 UTC

COMMIT: http://review.gluster.org/11128 committed in release-3.7 by Pranith Kumar Karampuri (pkarampu) 
------
commit 56becf03ffd0ddfae4fda4d064a1c91cf1eb57a6
Author: Pranith Kumar K <pkarampu>
Date:   Sun Jun 7 10:24:08 2015 +0530

    cluster/ec: Prevent double unwind
    
            Backport of http://review.gluster.com/11111
    
    Problem:
    1) ec_access/ec_readlink_/ec_readdir[p] _cbks are trying to recover only from
    ENOTCONN.
    2) When the fop succeeds it unwinds right away. But when its
    ec_fop_manager resumes, if the number of bricks that are up is less than
    ec->fragments, the the state machine will resume with -EC_STATE_REPORT which
    unwinds again. This will lead to crashes.
    
    Fix:
    - If fop fails retry on other subvols, as ESTALE/ENOENT/EBADFD etc are also
    recoverable.
    - unwind success/failure in _cbks
    
    BUG: 1229331
    Change-Id: I7510984a237761efba65e872313a8ede8b7543e5
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/11128
    Tested-by: Gluster Build System <jenkins.com>
    Tested-by: NetBSD Build System <jenkins.org>
    Reviewed-by: Xavier Hernandez <xhernandez>

Comment 3 Niels de Vos 2015-06-20 09:50:18 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.7.2, please reopen this bug report.

glusterfs-3.7.2 has been announced on the Gluster Packaging mailinglist [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://www.gluster.org/pipermail/packaging/2015-June/000006.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user