Whamcloud - gitweb
e2fsck: ignore badblocks if it says badblocks inode is bad
authorDarrick J. Wong <darrick.wong@oracle.com>
Thu, 11 Sep 2014 19:44:49 +0000 (12:44 -0700)
committerTheodore Ts'o <tytso@mit.edu>
Thu, 11 Sep 2014 22:08:26 +0000 (18:08 -0400)
commitc6c681632e45df376360303a00539b2a86ed7400
treee3cd0842f152ee415e140984a29e69114f05328e
parent3f4c4079976f1ccf0a6d675b0115b519f596da89
e2fsck: ignore badblocks if it says badblocks inode is bad

If the badblocks list says that the badblocks inode is bad, it's quite
likely that badblocks is broken.  Worse yet, if the root inode is in
the same block as the badblocks inode (likely since they're adjacent),
the filesystem becomes unfixable because pass3 notices the bad root
inode and exits.

So... if we encounter this case, just kill the badblocks inode.

Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
e2fsck/pass1.c
e2fsck/problem.c
e2fsck/problem.h
tests/f_bb_in_bb/expect.1 [new file with mode: 0644]
tests/f_bb_in_bb/expect.2 [new file with mode: 0644]
tests/f_bb_in_bb/image.gz [new file with mode: 0644]
tests/f_bb_in_bb/name [new file with mode: 0644]