From: Theodore Tso <tytso@mit.edu>
To: Kevin Shanahan <kmshanah@ucwb.org.au>
Cc: Eric Sandeen <sandeen@redhat.com>, linux-ext4@vger.kernel.org
Subject: Re: More ext4 corruption
Date: Sat, 4 Apr 2009 12:23:35 -0400 [thread overview]
Message-ID: <20090404162335.GC9812@mit.edu> (raw)
In-Reply-To: <20090404105226.GC5436@kulgan>
Hmm, what kernel version are you running at this point? Going through
your old e-mails I saw kernel log from 2.6.29-rc6; is that what you
are still running?
The symptoms seem to be the same as before --- something is writing
garbage into (apparently) a single 4k block, smashing part of your
inode table. It always seems to be a relatively low-numbered block.
This time, affecting inode numbers in the range of 369-375.
I don't remember if we've been through this procedure with you yet,
but if you haven't run fsck yet, find out the block number containing
the corrupted part of the inode table:
debugfs /dev/XXX
debugfs: imap <375>
Inode 375 is part of block group 0
located at block 88, offset 0x0600
And then do extract out the named block number like so:
dd if=/dev/XXX of=block88.dump bs=4k skip=88 count=1
then send us the 4k dump file, and let's see if we can see where it
came from. Maybe that will be a hint as to who or what wrote the
garbage to that location on disk.
- Ted
next prev parent reply other threads:[~2009-04-04 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 22:15 More ext4 corruption Kevin Shanahan
2009-04-03 23:25 ` Eric Sandeen
2009-04-04 10:52 ` Kevin Shanahan
2009-04-04 16:23 ` Theodore Tso [this message]
2009-04-04 21:39 ` Kevin Shanahan
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=20090404162335.GC9812@mit.edu \
--to=tytso@mit.edu \
--cc=kmshanah@ucwb.org.au \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.