Project

General

Profile

Actions
Copy link

Feature #7762

closed

journal-tool: backwards-search after corrupt regions

Added by John Spray about 10 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
John Spray
Category:
fsck/damage handling
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:

Description

When a corrupt region is encountered, use the start pointers to walk from the end of the log back to the latest valid entry. Combine with forwards search for sentinels to get max confidence about where valid LogEvents appear in the journal.

Actions
Copy link
 #1

Updated by Greg Farnum almost 8 years ago

  • Category changed from 66 to fsck/damage handling

We already have commands to harvest the latest versions of dentries and things, and I think we can punch holes and skip forward. So this is done now, right?

Actions
Copy link
 #2

Updated by John Spray almost 8 years ago

  • Status changed from New to Rejected

Hmm, iirc this ticket was about doing something smarter than scanning forward for a sentinel, where we would potentially start from the end of an object instead of the start.

As it's shaken out, I don't think we've seen a compelling case for actually doing that (we already use the start_ptr as a validation after we find a sentinel), so I'm going to close this.

Actions
Copy link

Also available in: Atom PDF