e2fsprogs/tests/f_h_badnode
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: When repacking directories, leave slack space for more efficiency 2008-12-25 17:59:36 -05:00
image.gz Add directory hashed signed/unsigned hint to superblock 2006-11-11 22:32:35 -05:00
name Add initial support for htree directories. 2002-06-25 23:26:34 -04:00
script Remove support for --enable-clear-htree; this was 2005-02-05 10:28:15 -05:00