| commit | e4230108547766f4e105a62c45f3724309106f91 | |
| author | Eric Sandeen <sandeen@redhat.com> | |
| Mon, 27 Aug 2012 19:30:40 +0000 (27 14:30 -0500) | ||
| committer | Jan Kara <jack@suse.cz> | |
| Mon, 3 Sep 2012 22:06:26 +0000 (4 00:06 +0200) | ||
| tree | 7aa54e8427892515c822939bd72ee9bd36afb5b0 | treesnapshot (tar.gz zip) |
| parent | da02eb72f150bef1d281d93b3e4716ce374c4510 | commitdiff |
ext3: don't clear orphan list on ro mount with errors
When we have a filesystem with an orphan inode list *and* in error
state, things behave differently if:
1) e2fsck -p is done prior to mount: e2fsck fixes things and exits
happily (barring other significant problems)
vs.
2) mount is done first, then e2fsck -p: due to the orphan inode
list removal, more errors are found and e2fsck exits with
UNEXPECTED INCONSISTENCY.
The 2nd case above, on the root filesystem, has the tendency to halt
the boot process, which is unfortunate.
The situation can be improved by not clearing the orphan
inode list when the fs is mounted readonly.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
When we have a filesystem with an orphan inode list *and* in error
state, things behave differently if:
1) e2fsck -p is done prior to mount: e2fsck fixes things and exits
happily (barring other significant problems)
vs.
2) mount is done first, then e2fsck -p: due to the orphan inode
list removal, more errors are found and e2fsck exits with
UNEXPECTED INCONSISTENCY.
The 2nd case above, on the root filesystem, has the tendency to halt
the boot process, which is unfortunate.
The situation can be improved by not clearing the orphan
inode list when the fs is mounted readonly.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>
| fs/ext3/super.c | diffblobblamehistory |