Actions
Bug #20471
closedCan't repair corrupt object info due to bad oid on all replicas
Status:
Resolved
Priority:
Urgent
Assignee:
David Zafman
Category:
Scrub/Repair
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(RADOS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
We detect a kind of corruption where the oid in the object info doesn't match the oid of the object. This was added at the request of http://tracker.ceph.com/issues/18409 in commit 9614ab556ca8e4e5daec1e71d9b6032633ba21a0.
I didn't anticipate the case where all versions of the object info have the same error. This would make it unrepairable.
According to Sam: "This came up on the sepia cluster due (presumably) to an xfs bug in the murky past." Assuming that this is caused by a bug in older bfs code we could add code to fix the object info and move on.
Actions