Actions
Feature #18513
closedMDS: scrub: forward scrub reports missing backtraces on new files as damage
Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:
0%
Source:
Development
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Description
It appears that running a recursive repair scrub_path results in reports of MDS damage on files that are new enough their backtraces haven't been persisted yet, even though
1) the backtrace isn't expected to be there yet, and
2) it then happily wrote it down correctly. (Well, I didn't check, but I presume.)
This is silly. Fix it!
Updated by Patrick Donnelly over 3 years ago
- Status changed from New to Resolved
This is fixed in the current code.
Actions