Bug 1339436 - 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: 3.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1339181
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-25 03:09 UTC by Krutika Dhananjay
Modified: 2016-06-16 12:32 UTC (History)
1 user (show)

Fixed In Version: glusterfs-3.8.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1339181
Environment:
Last Closed: 2016-06-16 12:32:10 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Krutika Dhananjay 2016-05-25 03:09:55 UTC
+++ This bug was initially created as a clone of Bug #1339181 +++

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:

--- Additional comment from Vijay Bellur on 2016-05-24 06:44:40 EDT ---

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 1 Vijay Bellur 2016-05-25 03:12:04 UTC
REVIEW: http://review.gluster.org/14527 (cluster/afr: Attempt name-index purge even on full-heal of directory) posted (#1) for review on release-3.8 by Krutika Dhananjay (kdhananj)

Comment 2 Vijay Bellur 2016-05-27 14:51:03 UTC
COMMIT: http://review.gluster.org/14527 committed in release-3.8 by Niels de Vos (ndevos) 
------
commit bc47e3255e35a2e02675d4d74e49138274b33f66
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
    
            Backport of: http://review.gluster.org/#/c/14516/
    
    Change-Id: I429ae628a310fd254bac7dde6d1e034d65608047
    BUG: 1339436
    Signed-off-by: Krutika Dhananjay <kdhananj>
    Reviewed-on: http://review.gluster.org/14527
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>

Comment 3 Niels de Vos 2016-06-16 12:32:10 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.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


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