[Bugs] [Bug 1499202] self-heal daemon stuck

bugzilla at redhat.com bugzilla at redhat.com
Mon Oct 9 06:52:55 UTC 2017


--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/18449 committed in release-3.12 by jiffin
tony Thottan (jthottan at redhat.com) 
commit f73814ad08d552d94d0139b2592175d206e7a166
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Wed Sep 20 12:16:06 2017 +0530

    afr: heal gfid as a part of entry heal

    If a brick crashes after an entry (file or dir) is created but before
    gfid is assigned, the good bricks will have pending entry heal xattrs
    but the heal won't complete because afr_selfheal_recreate_entry() tries
    to create the entry again and it fails with EEXIST.

    We could have fixed posx_mknod/mkdir etc to assign the gfid if the file
    already exists but the right thing to do seems to be to trigger a lookup
    on the bad brick and let it heal the gfid instead of winding an
    mknod/mkdir in the first place.

    (cherry picked from commit 20fa80057eb430fd72b4fa31b9b65598b8ec1265)
    Change-Id: I82f76665a7541f1893ef8d847b78af6466aff1ff
    BUG: 1499202
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>

You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.

More information about the Bugs mailing list