Actions
Feature #12131
opencephfs-data-scan: Update InoTable after injection
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, inodes are injected without any consideration to whether their number is still regarded as free in inotable.
This is okay in some cases (recovery for read-only retrieval of files, recovery where the inotable is not damaged), but in general we should add a step to the process that updates the inotable to ensure that injected inodes do not have numbers that are in the free range in the inotable.
cephfs-journal-tool already does something similar when scraping.
Actions