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_salvage_dir | |
| 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_salvage_dir')
| -rw-r--r-- | tests/f_salvage_dir/expect.1 | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/f_salvage_dir/expect.1 b/tests/f_salvage_dir/expect.1 index fc37883c..32863847 100644 --- a/tests/f_salvage_dir/expect.1 +++ b/tests/f_salvage_dir/expect.1 @@ -1,13 +1,13 @@ Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure -Directory inode 13, block 0, offset 48: directory corrupted +Directory inode 13, block #0, offset 48: directory corrupted Salvage? yes -Directory inode 12, block 1, offset 0: directory corrupted +Directory inode 12, block #1, offset 0: directory corrupted Salvage? yes Setting filetype for entry 'c' in /test (12) to 1. -Directory inode 12, block 1, offset 1016: directory corrupted +Directory inode 12, block #1, offset 1016: directory corrupted Salvage? yes Pass 3: Checking directory connectivity |