Bug 1339181 - Full heal of a sub-directory does not clean up name-indices when granular-entry-heal is enabled.
Summary: Full heal of a sub-directory does not clean up name-indices when granular-ent...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Krutika Dhananjay
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1339436
TreeView+ depends on / blocked
 
Reported: 2016-05-24 10:43 UTC by Krutika Dhananjay
Modified: 2017-03-27 18:11 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.9.0
Clone Of:
: 1339436 (view as bug list)
Environment:
Last Closed: 2017-03-27 18:11:33 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Krutika Dhananjay 2016-05-24 10:43:42 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Vijay Bellur 2016-05-24 10:44:40 UTC
REVIEW: http://review.gluster.org/14516 (cluster/afr: Attempt name-index purge even on full-heal of directory) posted (#1) for review on master by Krutika Dhananjay (kdhananj)

Comment 2 Vijay Bellur 2016-05-26 07:09:46 UTC
COMMIT: http://review.gluster.org/14516 committed in master by Pranith Kumar Karampuri (pkarampu) 
------
commit 04e3a343512d5f71266d334174afe44a6b8bbcfa
Author: Krutika Dhananjay <kdhananj>
Date:   Tue May 24 15:25:19 2016 +0530

    cluster/afr: Attempt name-index purge even on full-heal of directory
    
    Change-Id: Ief71cc68a4fbf8113e15b4254ebcabf7e30f74e2
    BUG: 1339181
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/14516
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Smoke: Gluster Build System <jenkins.com>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

Comment 3 Shyamsundar 2017-03-27 18:11:33 UTC
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.9.0, please open a new bug report.

glusterfs-3.9.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://lists.gluster.org/pipermail/gluster-users/2016-November/029281.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.