diff options
| author | Zhihao Cheng <chengzhihao1@huawei.com> | 2024-11-11 17:01:03 +0800 |
|---|---|---|
| committer | David Oberhollenzer <david.oberhollenzer@sigma-star.at> | 2024-11-11 10:32:45 +0100 |
| commit | e17ad291a8da970a4cf64a57796c30437d8c5fbd (patch) | |
| tree | 3b9df146f1111f13d73200f6250c6522226bf151 /tests/unittests/sysfs_mock/class/mtd/mtd0/flags | |
| parent | aa2b50294710caba39c6b01ce99f2f6993a42ed2 (diff) | |
fsck.ubifs: Add inconsistent problem handling asking function
There are four dimensions to define the type of inconsistent problems:
1. fixable: Some inconsistent problems can't be fixed, for example
corrupted superblock. Un-fixable problem will abort program.
2. must fix: Some inconsistent problems can be ignored(eg. incorrect
isize), but some are not(eg. corrupted TNC), which will affect the
subsequent fsck steps.
3. drop data: Some fixing methods will drop user data, which is
unacceptable for safe mode. If it happens, fsck will be aborted.
4. need rebuild: Some inconsistent problems depends on rebuilding
filesystem to be fixed(eg. corrupted master node, corrupted TNC).
Define an asking function to handle above kinds of inconsistent problems.
Signed-off-by: Zhihao Cheng <chengzhihao1@huawei.com>
Signed-off-by: David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Diffstat (limited to 'tests/unittests/sysfs_mock/class/mtd/mtd0/flags')
0 files changed, 0 insertions, 0 deletions