Actions
Feature #12138
opencephfs-data-scan: write inode backtraces when injecting to lost+found
Status:
New
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
Component(FS):
Labels (FS):
Pull request ID:
Description
Currently, for cases where we inject linkage for an inode into /lost+found, the inode's backtrace potentially still points somewhere else (like a stray dir, or somewhere we couldn't inject). That will cause a problem for any hardlinks pointing to the inode when they try to resolve its path.
When we inject something to lost+found, we should also update its backtrace so that anyone trying to resolve it by ino will know where to find it.
Updated by Greg Farnum almost 9 years ago
Hmm. When we do move something into lost+found, are we sure we can't make use of the backtrace any more, or might it still provide useful data? I think maybe we'd want to copy it somewhere rather than just overwriting it.
Updated by John Spray over 8 years ago
- Category changed from 66 to fsck/damage handling
Actions