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.
2x2 distributed replicated volume.
Version-Release number of selected component (if applicable):
One time issue.
Steps to Reproduce:
The files didn't heal , until "gluster volume heal volname full" is executed.
The files should either automatically heal, or can be manually heal by
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 (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/13861 committed in release-3.7 by Venky Shankar (email@example.com)
Author: Kotresh HR <firstname.lastname@example.org>
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.
Signed-off-by: Kotresh HR <email@example.com>
Smoke: Gluster Build System <firstname.lastname@example.org>
NetBSD-regression: NetBSD Build System <email@example.com>
CentOS-regression: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Venky Shankar <email@example.com>
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 , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.