Chapter 13. Self-heal does not complete
If a self-heal operation never completes, the cause could be a Gluster File ID (GFID) mismatch.
13.1. Gluster File ID mismatch
Check self-heal state.
Run the following command several times over a few minutes. Note the entries that are shown.
# gluster volume heal <volname> info
If the same entries are shown each time, these entries may have a GFID mismatch.
Check the GFID of each entry on each host.
On each host, run the following command for each entry:
# getfattr -d -m. -ehex <backend_path> -h
<backend_path>for an entry is comprised of the brick path and the entry. For example, if the brick for the
enginevolume has the path of
/gluster_bricks/engine/engineand the entry shown in heal info is
backend_pathto use is
Compare the output from each host.
trusted.gfidfor an entry is not the same on all hosts, there is a GFID mismatch.
Resolve the mismatch in favor of the GFID with the most recent modification time:
# gluster volume heal <volume> split-brain latest-mtime <entry>
# gluster volume heal engine split-brain latest-mtime /58d392a6-e5b1-4aed-9bbc-952210a7137d/ha_agent/hosted-engine.metadata
Manually trigger a heal on the volume.
# gluster volume heal <volname>