From: Andreas Dilger <adilger@sun.com>
To: Gary Hawco <ghawco@cox.net>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: Re: Add ext4__allow_read-only_mounts_with_corrupted_block_group_checksums patch
Date: Wed, 16 Jul 2008 03:29:14 -0600 [thread overview]
Message-ID: <20080716092914.GR6239@webber.adilger.int> (raw)
In-Reply-To: <3.0.6.32.20080715193126.0242c9a0@pop.west.cox.net>
On Jul 15, 2008 19:31 +0000, Gary Hawco wrote:
> Just recompiled 2.6.26 with the newest snapshot (15-July 2008/2310GMT).
> uninit_bg had been enabled.
>
> To test kernel I did: tune2fs -O ^uninit_bg /dev/sda6 to remove uninit_bg
> feature.
> Was prompted to run e2fsck on system.
>
> Rebooted and e2fsck saw errors and did a forced fsck without having to
> reboot. All is well thus far.
You shouldn't really have rebooted at that point, just run e2fsck on
the filesystem to clear the checksums.
> Then I did the reverse: tune2fs -O uninit_bg /dev/sda6 to renable uninit_bg
> feature. Again, I was prompted to run e2fsck on system.
Again, you should have just run e2fsck on the filesystem without rebooting,
in order to update the checksums.
> Rebooted. This time I got a kernel panic that started with:
> EXT4-fs: ext4_check_descriptors: Checksum for group 2 failed (10368!=32990)
> EXT4-fs: group descriptors corrupted!
The kernel thinks the filesystem is corrupted, so a full e2fsck needs to
be run. However, e2fsck is probably sitting on that unmountable filesystem.
> I was under the impression that the newest patch would handle this or am I
> mistaken?
We probably need to allow the kernel to mount the filesystem read-only in
this case in order to run e2fsck.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-07-16 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:31 Add ext4__allow_read-only_mounts_with_corrupted_block_group_checksums patch Gary Hawco
2008-07-16 9:29 ` Andreas Dilger [this message]
2008-07-16 13:34 ` Theodore Tso
2008-07-18 12:59 ` Theodore Tso
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080716092914.GR6239@webber.adilger.int \
--to=adilger@sun.com \
--cc=ghawco@cox.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox