e2fsprogs/tests/f_baddir2/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: 15/16 files (0.0% non-contiguous), 23/100 blocks
Exit status is 0
e2fsck: Fix salvage_directory when the last entry's rec_len is too big Recently, one of our customers found this message in pass2 of e2fsck while doing some regression testing: "Entry '4, 0x695a, 0x81ff, 0x0040, 0x8320, 0xa192, 0x0021' in ??? (136554) has rec_len of 14200, should be 26908." Both the displayed rec_len and the "should be" value are bogus. The reason is that salvage_directory sets a offset beyond blocksize leading to bogus messages. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 2007-07-09 21:05:45 +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: 15/16 files (0.0% non-contiguous), 23/100 blocks`
			`Exit status is 0`