Whamcloud - gitweb
e2fsck: Interpret negative blkcount in file system problem reports
authorTheodore Ts'o <tytso@mit.edu>
Sun, 4 Oct 2009 22:02:24 +0000 (18:02 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 4 Oct 2009 22:02:24 +0000 (18:02 -0400)
commit695706ca214d9d04666ee46a48f63f6127154a23
treeed8d82ae5dbb5f695bf486209e2a2d4b114e6ec2
parentf790bc33b20e5c1a9d357c41cb2c1b7ea486f98c
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>
e2fsck/message.c
e2fsck/problem.c
tests/f_badbblocks/expect.1
tests/f_baddir/expect.1
tests/f_baddir2/expect.1
tests/f_dupfsblks/expect.1
tests/f_h_badnode/expect.1
tests/f_h_badroot/expect.1
tests/f_h_reindex/expect.1
tests/f_salvage_dir/expect.1