Description of problem: Entries were found in indices/xattrop dir whose corresponding files had 0 value set for trusted.afr. xattrs. Such entries should be removed once known that heal is not required. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#1) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#2) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#3) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#4) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#5) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#6) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#7) for review on master by Ravishankar N (ravishankar)
REVIEW: http://review.gluster.org/9714 (afr: remove stale index entries) posted (#8) for review on master by Ravishankar N (ravishankar)
COMMIT: http://review.gluster.org/9714 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit c8be9af5f54aa3e42dffee4024d2915743258242 Author: Ravishankar N <ravishankar> Date: Thu Mar 5 11:29:25 2015 +0000 afr: remove stale index entries 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 transaction 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: I02cb2bc937f2e3f3f3cb35d67b006664dc7ef919 BUG: 1190069 Signed-off-by: Ravishankar N <ravishankar> Reviewed-on: http://review.gluster.org/9714 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Anuradha Talur <atalur> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Pranith Kumar Karampuri <pkarampu>
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.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user