Project

General

Profile

Feature #169

osd: start up despite corrupted pg log(s)

Added by Sage Weil over 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
OSD
Target version:
Start date:
06/02/2010
Due date:
% Done:

100%

Source:
Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Catch decoding, memory alloc exceptions, and skip corrupt pgs so the osd can still start up. Log the errors.


Related issues

Blocked by Ceph - Cleanup #435: osd: generalize coll_t to a string Resolved 09/24/2010

History

#1 Updated by Sage Weil over 9 years ago

  • Tracker changed from Bug to Feature
  • Priority changed from Normal to High

#2 Updated by Sage Weil over 9 years ago

  • Target version set to v0.21

#3 Updated by Sage Weil about 9 years ago

  • Priority changed from High to Low
  • Target version deleted (v0.21)

Dropping the priority on this, now that the corruption in #212 is fixed.

#4 Updated by Sage Weil almost 9 years ago

  • Priority changed from Low to Normal

#5 Updated by Sage Weil almost 9 years ago

  • Category set to OSD

#6 Updated by Sage Weil almost 9 years ago

First, we need to catch any buffer::error exceptions during pg log parsing.

Then, we need to decide what to do about it. How about making a 'corrupt' (or similar) subdir, and stashing the bad pg logs there? Then starting up with a zeroed log.

#7 Updated by Sage Weil almost 9 years ago

  • Priority changed from Normal to High
  • Target version set to v0.22

#8 Updated by Sage Weil almost 9 years ago

  • Target version changed from v0.22 to v0.23

#9 Updated by Colin McCabe almost 9 years ago

  • % Done changed from 0 to 100

Done. We put each corrupt page log in a new collection.

#10 Updated by Sage Weil almost 9 years ago

  • Status changed from New to Testing

#11 Updated by Sage Weil almost 9 years ago

  • Status changed from Testing to Resolved

Also available in: Atom PDF