e2fsprogs/tests/f_idata_and_extents
Darrick J. Wong fa441f91f1 e2fsck: fix conflicting extents|inlinedata inode flags
If we come across an inode with the inline data and extents inode flag
set, try to figure out the correct flag settings from the contents of
i_block and i_size.  If i_blocks looks like an extent tree head, we'll
make it an extent inode; if it's small enough for inline data, set it
to that.  This leaves the weird gray area where there's no extent
tree but it's too big for the inode -- if /could/ be a block map,
change it to that; otherwise, just clear the inode.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
2014-08-10 18:43:24 -04:00
..
expect.1 e2fsck: fix conflicting extents|inlinedata inode flags 2014-08-10 18:43:24 -04:00
expect.2 e2fsck: fix conflicting extents|inlinedata inode flags 2014-08-10 18:43:24 -04:00
image.gz e2fsck: fix conflicting extents|inlinedata inode flags 2014-08-10 18:43:24 -04:00
name e2fsck: fix conflicting extents|inlinedata inode flags 2014-08-10 18:43:24 -04:00