| commit | 695706ca214d9d04666ee46a48f63f6127154a23 | [log] [tgz] |
|---|---|---|
| author | Theodore Ts'o <tytso@mit.edu> | Sun Oct 04 18:02:24 2009 -0400 |
| committer | Theodore Ts'o <tytso@mit.edu> | Sun Oct 04 18:02:24 2009 -0400 |
| tree | ed8d82ae5dbb5f695bf486209e2a2d4b114e6ec2 | |
| parent | f790bc33b20e5c1a9d357c41cb2c1b7ea486f98c [diff] |
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>