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

REVIEW: http://review.gluster.org/11111 (cluster/ec: Prevent double unwind) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu)

REVIEW: http://review.gluster.org/11111 (cluster/ec: Prevent double unwind) posted (#3) for review on master by Pranith Kumar Karampuri (pkarampu)

COMMIT: http://review.gluster.org/11111 committed in master by Vijay Bellur (vbellur) 
------
commit 31866a490edf5b92886accac67eddf78b291d710
Author: Pranith Kumar K <pkarampu>
Date:   Sun Jun 7 10:24:08 2015 +0530

    cluster/ec: Prevent double unwind
    
    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
    
    Change-Id: I2cac3c2f9669a4e6160f1ff4abc39f0299303222
    BUG: 1228952
    Signed-off-by: Pranith Kumar K <pkarampu>
    Reviewed-on: http://review.gluster.org/11111
    Reviewed-by: Xavier Hernandez <xhernandez>
    Tested-by: Gluster Build System <jenkins.com>

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.

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