vitalif
/
e2fsprogs
mirror of https://github.com/vitalif/e2fsprogs
1
0
Fork 0
Code Issues Releases Wiki Activity
e2fsprogs/tests/f_baddir2
History
Theodore Ts'o 695706ca21 e2fsck: Interpret negative blkcount in file system problem reports 
Non-expert users get confused when they see messages like this:

Illegal block #-1 (2291965952) in inode 176. CLEARED.

So change it to be something a little bit more understandable:

Illegal indirect block (2291965952) in inode 176.  CLEARED.

Addresses-SourceForge-Bug: #2871782

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
 		2009-10-04 18:02:24 -04:00
..
expect.1 e2fsck: Interpret negative blkcount in file system problem reports 2009-10-04 18:02:24 -04:00
expect.2 e2fsck: Fix salvage_directory when the last entry's rec_len is too big 2007-07-10 07:28:35 -04:00
image.gz e2fsck: Fix salvage_directory when the last entry's rec_len is too big 2007-07-10 07:28:35 -04:00
name e2fsck: Fix salvage_directory when the last entry's rec_len is too big 2007-07-10 07:28:35 -04:00