e2fsprogs/tests/f_zeroed_ext_header/expect.2

Pass 1: Checking inodes, blocks, and sizes
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 (0.0% non-contiguous), 15/256 blocks
Exit status is 0
e2fsck: zap extent-format inode with no extent header The kernel requires all inodes with the extent flag set to have a valid extent tree header in i_block. The ext2fs_extent_open2 prefers to initialize the header if i_block is zeroed, but e2fsck never writes the new header to disk. Since the kernel won't create inodes with the flag and no header anyway, zap such files. Reported-by: Bo Branten <bosse@acc.umu.se> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 2015-11-30 23:22:07 +03:00			`Pass 1: Checking inodes, blocks, and sizes`
			`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 (0.0% non-contiguous), 15/256 blocks`
			`Exit status is 0`