Feature #169
closed
osd: start up despite corrupted pg log(s)
Added by Sage Weil almost 14 years ago.
Updated over 13 years ago.
Description
Catch decoding, memory alloc exceptions, and skip corrupt pgs so the osd can still start up. Log the errors.
- Tracker changed from Bug to Feature
- Priority changed from Normal to High
- Target version set to v0.21
- Priority changed from High to Low
- Target version deleted (
v0.21)
Dropping the priority on this, now that the corruption in #212 is fixed.
- Priority changed from Low to Normal
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.
- Priority changed from Normal to High
- Target version set to v0.22
- Target version changed from v0.22 to v0.23
- % Done changed from 0 to 100
Done. We put each corrupt page log in a new collection.
- Status changed from New to 7
- Status changed from 7 to Resolved
Also available in: Atom
PDF