e2fsprogs/tests/f_hugedir_blocks/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 (8.3% non-contiguous), 22/512 blocks
Exit status is 0
e2fsck: pass2 should not process directory blocks that are impossibly large Currently, directories cannot be fallocated, which means that the only way they get bigger is for the kernel to append blocks one by one. Therefore, if we encounter a logical block offset that is too big, we needn't bother adding it to the dblist for pass2 processing, because it's unlikely to contain a valid directory block. The code that handles extent based directories also does not add toobig blocks to the dblist. Note that we can easily cause e2fsck to fail with ENOMEM if we start feeding it really large logical block offsets, as the dblist implementation will try to realloc() an array big enough to hold it. Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com> Signed-off-by: Theodore Ts'o <tytso@mit.edu> 2014-07-25 16:41:11 +04: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 (8.3% non-contiguous), 22/512 blocks`
			`Exit status is 0`