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	Many files:	1997-04-26 14:37:06 +00:00
image.gz	Many files:	1997-04-26 14:00:26 +00:00
name	Many files:	1997-04-26 14:00:26 +00:00