e2fsprogs/tests/f_inlinedata_dirblocks/expect.1
Darrick J. Wong 0ac4b3973f e2fsck: inspect inline dir data as two directory blocks
The design of inline directories (apparently) calls for the i_block[]
region and the EA regions to be treated as if they were two separate
blocks of dirents.  Effectively this means that it is impossible for a
directory entry to straddle both areas.  e2fsck doesn't enforce this,
so teach it to do so.  e2fslib already knows to do this....

Cc: Zheng Liu <gnehzuil.liu@gmail.com>
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2015-01-28 09:00:13 -05:00

26 lines
720 B
Groff

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry '..' in ??? (12) has invalid inode #: 1752440867.
Clear? yes
Directory inode 12, block #0, offset 4: directory corrupted
Salvage? yes
Directory inode 12, block #1, offset 0: directory corrupted
Salvage? yes
Pass 3: Checking directory connectivity
'..' in /aoo (12) is ??? (1752440867), should be / (2).
Fix? yes
Error while adjusting inode count on inode 0
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Directories count wrong for group #0 (2, counted=3).
Fix? yes
test_filesys: ***** FILE SYSTEM WAS MODIFIED *****
test_filesys: 12/128 files (0.0% non-contiguous), 17/512 blocks
Exit status is 1