From: Ron Johnson <ron.l.johnson@cox.net>
To: Linux-Ext4 <linux-ext4@vger.kernel.org>
Subject: Re: EXT4-fs: group descriptors corrupted!
Date: Wed, 25 Feb 2009 15:47:15 -0600 [thread overview]
Message-ID: <49A5BC63.9030104@cox.net> (raw)
In-Reply-To: <20090225213046.GF1363@mit.edu>
On 02/25/2009 03:30 PM, Theodore Tso wrote:
> On Wed, Feb 25, 2009 at 02:39:31PM -0600, Ron Johnson wrote:
>> These are the relevant Debian Sid package versions:
>> e2fsprogs 1.41.3-1
>> linux-source-2.6.28 2.6.28-2~snapshot.12850
>>
>> Since I built the fs with extents enabled, I am hesitant to run fsck on
>> it because I've read that it doesn't yet support extents.
>>
>> As you can see from the dmesg snippets, one of my ext4 file systems
>> mounted perfectly. The one that didn't is an lvm2 "array", which seems
>> to be consistent.
>
> E2fsck 1.41.3 does actually have extent support, but let's not be too
> hasty to run e2fsck just yet.
>
> Can you send me the output of "dumpe2fs -o superblock=32768
> /dev/main_huge_vg/main_huge_lv" and see how it compares to the
> dumpe2fs of your primary superblock?
# dumpe2fs -f -o superblock=32768 /dev/main_huge_vg/main_huge_lv |
head -n800 > main_huge_lv.dump.sb32768.txt
dumpe2fs 1.41.3 (12-Oct-2008)
ext2fs_read_bb_inode: Invalid argument
http://members.cox.net/ron.l.johnson/main_huge_lv.dump.sb32768.txt
> It looks like your block group descriptors were totally scribbled
> upon.
There system cleanly shut down. (Or, at least, I didn't notice
anything obviously wrong.)
> How and why it happened, I'm not sure. But before we do
> anything else, let's check out the backup descriptors and make sure
> they are sane.
--
Ron Johnson, Jr.
Jefferson LA USA
The feeling of disgust at seeing a human female in a Relationship
with a chimp male is Homininphobia, and you should be ashamed of
yourself.
next prev parent reply other threads:[~2009-02-25 22:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:39 EXT4-fs: group descriptors corrupted! Ron Johnson
2009-02-25 21:30 ` Theodore Tso
2009-02-25 21:47 ` Ron Johnson [this message]
2009-02-25 23:18 ` Theodore Tso
2009-02-25 23:41 ` Greg Freemyer
2009-02-25 23:42 ` Ron Johnson
2009-02-26 0:05 ` Andreas Dilger
2009-02-26 0:23 ` Ron Johnson
-- strict thread matches above, loose matches on Subject: below --
2009-03-07 6:55 Christian
2009-03-09 16:13 ` Christian
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=49A5BC63.9030104@cox.net \
--to=ron.l.johnson@cox.net \
--cc=linux-ext4@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).