Actions
Feature #16016
closedPopulate DamageTable from forward scrub
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
jewel
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:
Description
We detect metadata damage two ways: when we try to read things off disk during normal operation, and when we try to verify what's on disk during forward scrub.
Currently DamageTable is only populated in the first path. The issues detected by forward scrub go to the cluster log, but are not visible to the user when they subsequently go to dump the damage table.
Update the forward scrub code to populate DamageTable when it finds errors.
Updated by John Spray over 7 years ago
- Status changed from New to Fix Under Review
Updated by John Spray over 7 years ago
- Status changed from Fix Under Review to Resolved
Updated by Nathan Cutler almost 7 years ago
- Status changed from Resolved to Pending Backport
Updated by Nathan Cutler almost 7 years ago
- Copied to Backport #20294: jewel: Populate DamageTable from forward scrub added
Updated by Nathan Cutler over 6 years ago
- Status changed from Pending Backport to Resolved
Actions