Bug 1322552

Summary:	Self-heal and manual heal not healing some file
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	glusterfind	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.7.9	CC:	avishwan, bugs, khiremat, pkarampu, ravishankar, rhs-bugs, rnalakka, sanandpa
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	glusterfs-3.7.10	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1321955	Environment:
Last Closed:	2016-04-19 07:01:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1317908, 1321955
Bug Blocks:

Comment 1 Kotresh HR 2016-03-30 17:38:37 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

Comment 2 Vijay Bellur 2016-03-30 17:54:51 UTC

REVIEW: http://review.gluster.org/13861 (features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path') posted (#1) for review on release-3.7 by Kotresh HR (khiremat)

Comment 3 Vijay Bellur 2016-03-31 15:56:18 UTC

COMMIT: http://review.gluster.org/13861 committed in release-3.7 by Venky Shankar (vshankar) 
------
commit 5560961e5188c6b8f4b09d57245513a8f9612ff4
Author: Kotresh HR <khiremat>
Date:   Tue Mar 29 19:06:46 2016 +0530

    features/changelog: Don't modify 'pargfid' in 'resolve_pargfid_to_path'
    
    Backport of http://review.gluster.org/#/c/13845/
    
    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.
    
    BUG: 1322552
    Change-Id: I9f2bc44b5604b224462594c12b7d79e68198d693
    Signed-off-by: Kotresh HR <khiremat>
    Reviewed-on: http://review.gluster.org/13861
    Smoke: Gluster Build System <jenkins.com>
    NetBSD-regression: NetBSD Build System <jenkins.org>
    CentOS-regression: Gluster Build System <jenkins.com>
    Reviewed-by: Venky Shankar <vshankar>

Comment 4 Kaushal 2016-04-19 07:01:21 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.7.10, please open a new bug report.

glusterfs-3.7.10 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] https://www.gluster.org/pipermail/gluster-users/2016-April/026164.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user