vitalif
/
e2fsprogs
mirror of https://github.com/vitalif/e2fsprogs
1
0
Fork 0
Code Issues Releases Wiki Activity
e2fsprogs/tests/f_extent_int_bad_csum/expect.1

12 lines
413 B
Groff
Raw Normal View History

tests: add tests for handling of corrupt extents Add some regression tests to examine how e2fsck deals with (a) extent blocks with only a bad checksum; (b) extent blocks with a bad magic number; and (c) extent entries with corruption. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2014-08-01 22:13:14 +04:00
Pass 1: Checking inodes, blocks, and sizes
Inode 12 extent block passes checks, but checksum does not match extent
e2fsck: remove 'invalid' wording from error when extent block fails checksum Don't say the physical block number is invalid if an extent block fails only the checksum. It passes checks, so it's not invalid. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2014-12-03 08:01:44 +03:00
(logical block 698, physical block 1788, len 1)
tests: add tests for handling of corrupt extents Add some regression tests to examine how e2fsck deals with (a) extent blocks with only a bad checksum; (b) extent blocks with a bad magic number; and (c) extent entries with corruption. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2014-08-01 22:13:14 +04:00
Fix? yes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
test_filesys: 12/128 files (16.7% non-contiguous), 1446/2048 blocks
Exit status is 0