Bug #20471: Can't repair corrupt object info due to bad oid on all replicas - RADOS - Ceph

Actions

Copy link

Bug #20471

closed

Can't repair corrupt object info due to bad oid on all replicas

Added by David Zafman almost 7 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

David Zafman

Category:

Scrub/Repair

Target version:

% Done:

Source:

Development

Tags:

Backport:

jewel

Regression:

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.

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by David Zafman almost 7 years ago

Status changed from 12 to In Progress

2017-06-30 15:55:46.845656 osd.1 [INF] 1.6 scrub starts
2017-06-30 15:55:46.847427 osd.0 [ERR] osd.0 found object info error on pg 1.6 oid 1:602f83fe:::foo:head oid in object info: 1:602f83fe:::boo:head...repaired
2017-06-30 15:55:46.847427 osd.1 [ERR] osd.1 found object info error on pg 1.6 oid 1:602f83fe:::foo:head oid in object info: 1:602f83fe:::boo:head...repaired
2017-06-30 15:55:46.847433 osd.2 [ERR] osd.2 found object info error on pg 1.6 oid 1:602f83fe:::foo:head oid in object info: 1:602f83fe:::boo:head...repaired
2017-06-30 15:55:46.849443 osd.1 [INF] 1.6 scrub ok

Actions

Copy link