mirror of
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git
synced 2024-11-23 10:04:01 +08:00
ce75cf5459
If e2fsck can optimize an inode's extent tree, it should ask for permission to optimize it, not to "fix" it. This was causing some confusion, since some users interpreted this prompt as an indication that the file system was inconsistent. Signed-off-by: Theodore Ts'o <tytso@mit.edu>
27 lines
713 B
Groff
27 lines
713 B
Groff
Pass 1: Checking inodes, blocks, and sizes
|
|
Inode 12 has an invalid extent node (blk 22, lblk 0)
|
|
Clear? yes
|
|
|
|
Inode 12 extent tree (at level 1) could be shorter. Optimize? yes
|
|
|
|
Inode 12, i_blocks is 16, should be 8. Fix? yes
|
|
|
|
Pass 1E: Optimizing extent trees
|
|
Pass 2: Checking directory structure
|
|
Pass 3: Checking directory connectivity
|
|
Pass 4: Checking reference counts
|
|
Pass 5: Checking group summary information
|
|
Block bitmap differences: -(21--23) -25
|
|
Fix? yes
|
|
|
|
Free blocks count wrong for group #0 (73, counted=77).
|
|
Fix? yes
|
|
|
|
Free blocks count wrong (73, counted=77).
|
|
Fix? yes
|
|
|
|
|
|
test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
|
|
test_filesys: 12/16 files (0.0% non-contiguous), 23/100 blocks
|
|
Exit status is 1
|