Bug 1238508

REVIEW: http://review.gluster.org/11498 (cluster/afr : expunge first, impunge next in entry selfheal) posted (#1) for review on master by Anuradha Talur (atalur)

REVIEW: http://review.gluster.org/11498 (cluster/afr : expunge first, impunge next in entry selfheal) posted (#2) for review on master by Anuradha Talur (atalur)

REVIEW: http://review.gluster.org/11498 (cluster/afr : expunge first, impunge next in entry selfheal) posted (#3) for review on master by Anuradha Talur (atalur)

REVIEW: http://review.gluster.org/11498 (cluster/afr : expunge first, impunge next in entry selfheal) posted (#4) for review on master by Anuradha Talur (atalur)

REVIEW: http://review.gluster.org/11498 (cluster/afr : expunge first, impunge next in entry selfheal) posted (#5) for review on master by Anuradha Talur (atalur)

COMMIT: http://review.gluster.org/11498 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 214101394bdea4ab57b8704467f450df4adbb8f6
Author: Anuradha Talur <atalur>
Date:   Fri Jul 3 11:35:46 2015 +0530

    cluster/afr : expunge first, impunge next in entry selfheal
    
    When entry self-heals are performed, the files/directories
    that are to be expunged should be removed first and then
    impunge should be done.
    
    Consider the following scenario :
    A volume with 2 bricks : b0 and b1.
    1) With following hierarchy on both bricks:
    olddir
    |__ oldfile
    
    2) Bring down b1 and do 'mv olddir newdir'.
    
    3) Bring up b1 and self-heal.
    
    4) Without patch, during self-heal the events occur in
    following order,
            a) Creation of newdir on the sink brick. Notice that
    gfid of olddir and newdir are same. As a result of which
    gfid-link file in .glusterfs directory still points to olddir
    and not to newdir.
    
            b) Deletion of olddir on the sink brick. As a part of
    this deletion, the gfid link file is also deleted. Now, there
    is no link file pointing to newdir.
    
    5) Files under newdir will not get listed as part of readdir.
    
    To tackle this kind of scenario, an expunge should be done first
    and impunge later; which is the purpose of this patch.
    
    Change-Id: Idc8546f652adf11a13784ff989077cf79986bbd5
    BUG: 1238508
    Signed-off-by: Anuradha Talur <atalur>
    Reviewed-on: http://review.gluster.org/11498
    Reviewed-by: Ravishankar N <ravishankar>
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Krutika Dhananjay <kdhananj>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

REVIEW: http://review.gluster.org/11556 (tests: Fix ./tests/bugs/replicate/bug-1238508-self-heal.t) posted (#1) for review on master by Ravishankar N (ravishankar)

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