19.3. Restore a bad file
-oaux-gfid-mountmount option, and enable GFID-to-path translation on each volume by running the following command.
# gluster volume set VOLNAME build-pgfid on
Procedure 19.1. Restoring a bad file from a replicate volume
Note the identifiers of bad filesCheck the output of the
scrub statuscommand to determine the identifiers of corrupted files.
# gluster volume bitrot VOLNAME scrub status Volume name: VOLNAME ... Node name: NODENAME ... Error count: 3 Corrupted objects: 5f61ade8-49fb-4c37-af84-c95041ff4bf5 e8561c6b-f881-499b-808b-7fa2bce190f7 eff2433f-eae9-48ba-bdef-839603c9434c
Determine the path of each corrupted objectFor files created after GFID-to-path translation was enabled, use the
getfattrcommand to determine the path of the corrupted files.
# getfattr -n glusterfs.ancestry.path -e text /mnt/VOLNAME/.gfid/GFID ... glusterfs.ancestry.path="/path/to/corrupted_file"For files created before GFID-to-path translation was enabled, use the
findcommand to determine the path of the corrupted file and the index file that match the identifying GFID.
# find /rhgs/brick*/.glusterfs -name GFID /rhgs/brick1/.glusterfs/path/to/GFID
# find /rhgs -samefile /rhgs/brick1/.glusterfs/path/to/GFID /rhgs/brick1/.glusterfs/path/to/GFID /rhgs/brick1/path/to/corrupted_file
Delete the corrupted filesDelete the corrupted files from the path output by the
Delete the GFID fileDelete the GFID file from the
Heal the fileIf you have client self-heal enabled, the file is healed the next time that you access it.If you do not have client self-heal enabled, you must manually heal the volume with the following command.
# gluster volume heal VOLNAMEThe next time that the bitrot scrubber runs, this GFID is no longer listed (unless it has become corrupted again).