Bug 1321955 - Self-heal and manual heal not healing some file
Summary: Self-heal and manual heal not healing some file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterfind
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Kotresh HR
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On: 1317908
Blocks: 1322552
TreeView+ depends on / blocked
 
Reported: 2016-03-29 13:08 UTC by Kotresh HR
Modified: 2016-06-16 14:02 UTC (History)
7 users (show)

Fixed In Version: glusterfs-3.8rc2
Clone Of: 1317908
: 1322552 (view as bug list)
Environment:
Last Closed: 2016-06-16 14:02:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Comment 1 Kotresh HR 2016-03-29 13:10:19 UTC
Description of problem:

Rebooted one among the four gluster nodes, after the reboot when checked the "heal info" there were 6 files listed for healing. The files didn't heal by the self-heal daemon. Tried to perform manual heal, didn't succeed. 
Finally he need to run "gluster volume heal volname full" for the 6 files to get healed.
Environment : 

2x2 distributed replicated volume. 


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


How reproducible:

One time issue. 

Steps to Reproduce:

N A 

Actual results:

The files didn't heal , until "gluster volume heal volname full" is executed. 


Expected results:

The files should either automatically heal, or can be manually heal by 
 
gluster volume heal volume name.

Comment 2 Vijay Bellur 2016-03-29 13:58:43 UTC
REVIEW: http://review.gluster.org/13845 (features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path') posted (#1) for review on master by Kotresh HR (khiremat)

Comment 3 Vijay Bellur 2016-03-29 14:34:29 UTC
REVIEW: http://review.gluster.org/13845 (features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path') posted (#2) for review on master by Kotresh HR (khiremat)

Comment 4 Vijay Bellur 2016-03-29 17:56:02 UTC
REVIEW: http://review.gluster.org/13845 (features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path') posted (#3) for review on master by Kotresh HR (khiremat)

Comment 5 Vijay Bellur 2016-03-30 05:53:18 UTC
REVIEW: http://review.gluster.org/13845 (features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path') posted (#4) for review on master by Kotresh HR (khiremat)

Comment 6 Vijay Bellur 2016-03-31 04:23:26 UTC
COMMIT: http://review.gluster.org/13845 committed in master by Venky Shankar (vshankar) 
------
commit 9746ee75865162af1827337f22a553ea0c3ba2ed
Author: Kotresh HR <khiremat>
Date:   Tue Mar 29 19:06:46 2016 +0530

    features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path'
    
    If 'changelog' is enabled and 'changelog.capture-del-path' option is on
    it calls 'resolve_pargfid_to_path' which modifies 'pargfid' sent by
    caller.  'changelog_unlink' calls this routine directly with
    'loc->pargfid' resulting it being modified and point to root instead of
    actual pargfid. This is a nasty bug and could cause the deletion of
    entry on root directory instead on actual parent when 'loc->path' is
    not present.  Hence this fix to make 'pargfid' a const pointer and
    'resolve_pargfid' to work on copy of pargfid.
    
    Glusterfind session creation enables these options by default to
    capture deleted entry path in changelog.
    
    Thanks Pranith for root causing this.
    
    Change-Id: I1d275a86f91c981b6889bedef93401c039d01d71
    BUG: 1321955
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/13845
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    Reviewed-by: Pranith Kumar Karampuri <pkarampu>
    Reviewed-by: Venky Shankar <vshankar>
    Reviewed-by: Ravishankar N <ravishankar>
    CentOS-regression: Gluster Build System <jenkins.com>

Comment 7 Niels de Vos 2016-06-16 14:02:08 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.