Bug 1266015 - Not able to recover the corrupted file on Replica volume
Summary: Not able to recover the corrupted file on Replica volume
Keywords:
Status: CLOSED DUPLICATE of bug 1238171
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: bitrot
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Venky Shankar
QA Contact: Sweta Anandpara
URL:
Whiteboard:
Depends On: 1238171
Blocks: 1216951 1238188 1255604 1255689 1266014
TreeView+ depends on / blocked
 
Reported: 2015-09-24 10:16 UTC by Vivek Agarwal
Modified: 2018-03-13 09:59 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
When an inode is unlinked from the backend (bricks) directly, the corresponding in-memory inode is not cleaned on subsequent lookup. This causes the recovery procedure using healing damons (such as AFR/EC self-heal) to not function as expected as the in-memory inode structure represents a corrupted backend object. Workaround: The object can be deleted directly from the backend and hence the next lookup on the object fails and the inode is forgotten. Now, the self heal daemon heals the object from the good copy.
Clone Of: 1238171
Environment:
Last Closed: 2018-03-13 09:59:15 UTC
Embargoed:

Attachments (Terms of Use)

Comment 3 Anjana Suparna Sriram 2015-09-28 06:47:34 UTC 
Hi Raghavendra,

Could you please review the edited doc text and sign off for technical accuracy.

Regards,
Anjana
Comment 4 Raghavendra Bhat 2015-09-29 12:16:31 UTC 
If the object is deleted directly from the backend, then one does not have to wait till the inode to be forgotten. The next lookup on the object fails and the inode is forgotten right away and lets self heal daemon heal the object from the good copy.
Comment 5 Anjana Suparna Sriram 2015-09-29 12:29:34 UTC 
Edited further as per our discussion; please review and sign off.
Comment 6 Raghavendra Bhat 2015-09-29 12:34:56 UTC 
Looks good to me.
Comment 9 Amar Tumballi 2018-03-13 09:59:15 UTC 

*** This bug has been marked as a duplicate of bug 1238171 ***
Note You need to log in before you can comment on or make changes to this bug.