Description of problem: ======================= Not able to recover the corrupted file on Replica volume Version-Release number of selected component (if applicable): ========== glusterfs-api-3.7.1-6 How reproducible: Steps to Reproduce: ========================== 1.Create 1X2 volume and enable bitrot, once the file is signed modify the file directly from the brick on any of the node 2.Once scrubber marks the file as bad , trying to recover the file by running following steps 3. Get the gfid of the corrupted file by running the getfattr -d -m . -e hex <filename> 4. Delete the corrupted file directly from the back-end 5. Go to the /brick/.glsuterfs and delete the gfid file 6. From the FUSE mount access the corrupted file 7. Run gluster volume heal volname to get the deleted corrupted file Actual results: Self heal is failing Expected results: User should be able to recover the bad file Setup details: IP:10.70.36.26/29
Doc text is edited. Please sign off to be included in Known Issues.
doc text looks good.
Tested with "glusterfs-server-3.7.1-12", able to recover the bad file from the replica volume so marking this as verified
Tested with 3.1.1 build and manually able to recover the bad file from replica volume
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1845.html
*** Bug 1266014 has been marked as a duplicate of this bug. ***
*** Bug 1266015 has been marked as a duplicate of this bug. ***