[Bugs] [Bug 1203081] Entries in indices/xattrop directory not removed appropriately

bugzilla at redhat.com bugzilla at redhat.com
Wed Mar 25 08:57:10 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1203081



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/9920 committed in release-3.6 by Raghavendra
Bhat (raghavendra at redhat.com) 
------
commit e4d8dc2e80f0683c69481c47875c01c8c3723814
Author: Ravishankar N <ravishankar at redhat.com>
Date:   Wed Mar 18 10:30:12 2015 +0530

    afr: remove stale index entries

    Backport of http://review.gluster.org/9714

    Problem:
    During pre-op phase, the index xlator
    1. Creates the entry inside .glusterfs/indices/xattrop
    2. Winds the xattrop fop to posix to mark dirty/pending changelogs.
    If the brick crashes after 1, the xattrop entry becomes stale and never
    gets removed by shd during subsequent crawls because there is nothing to
    heal (changelogs are zero).

    Though the stale entry does not get displayed in the output of 'heal info'
    command, it nevertheless stays there forever unless a new write tansaction
    is performed on the file.

    Fix:
    During index self-heal if afr xattrs are found to be clean (indicated by
    ret value of 2 on a call to afr_shd_selfheal(), send a dummy
    post-op with all 0s for the xattr values, which makes the index xlator
    to unlink the stale entry.

    Change-Id: Iffb171e40490abd8d44df09ccc058b5da67baafe
    BUG: 1203081
    Signed-off-by: Ravishankar N <ravishankar at redhat.com>
    Reviewed-on: http://review.gluster.org/9920
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
    Reviewed-by: Raghavendra Bhat <raghavendra at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=T3Po3T5H3L&a=cc_unsubscribe


More information about the Bugs mailing list