diff options
| author | Theodore Ts'o <tytso@mit.edu> | 2009-10-04 18:02:24 -0400 |
|---|---|---|
| committer | Theodore Ts'o <tytso@mit.edu> | 2009-10-04 18:02:24 -0400 |
| commit | 695706ca214d9d04666ee46a48f63f6127154a23 (patch) | |
| tree | ed8d82ae5dbb5f695bf486209e2a2d4b114e6ec2 /tests/f_baddir | |
| parent | f790bc33b20e5c1a9d357c41cb2c1b7ea486f98c (diff) | |
| download | e2fsprogs-695706ca214d9d04666ee46a48f63f6127154a23.tar.gz | |
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>
Diffstat (limited to 'tests/f_baddir')
| -rw-r--r-- | tests/f_baddir/expect.1 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/f_baddir/expect.1 b/tests/f_baddir/expect.1 index 52f0d20d..39735061 100644 --- a/tests/f_baddir/expect.1 +++ b/tests/f_baddir/expect.1 @@ -19,7 +19,7 @@ Clear? yes Entry 'dot' in /test (14) is a link to '.' Clear? yes -Directory inode 12, block 0, offset 0: directory corrupted +Directory inode 12, block #0, offset 0: directory corrupted Salvage? yes Missing '.' in directory inode 12. |