From: Eric Sandeen <sandeen@sandeen.net>
To: Karl Pickett <karl.pickett@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG when using corrupted ext3 fs
Date: Mon, 11 Jun 2007 15:04:41 -0500 [thread overview]
Message-ID: <466DAAD9.2030207@sandeen.net> (raw)
In-Reply-To: <f9be06770706080753m41959da2m2034e428854c1c0b@mail.gmail.com>
Karl Pickett wrote:
> I had to hard shutdown a fc6 machine due to vmware and nvidia doing
> ridiculous things to my screen resolution and locking up. ugh.
> Anyway, upon reboot it recovers the journal and mounts / rw fine.
> Then rc.sysinit tries to delete various things from /tmp (.ICE-unix,
> .font stuff, etc), kernel shows a BUG, and boot stops. Booting from a
> fc7 live cd and trying to mount /dev/sda2 rw and delete /tmp/* also
> causes a BUG. This dump is from fc7:
>
...
The corrupted orphan inode list bug I fixed,
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2988a7740dc0dd9a0cb56576e8fe1d777dff0db3
is in that fc7 kernel, so that's probably not it (though your fc6 kernel
probably didn't have that fix) (it's related to link & unlink racing)
Perhaps this could be related to Vasily's issue w/ bad_inodes not
getting removed from the list ?
[RFC PATCH ext3/ext4] orphan list corruption due bad inode
http://lkml.org/lkml/2007/6/4/7
I haven't looked at all the ways we could get bad inodes on the orphan
inode list, and not properly removed...
-Eric
prev parent reply other threads:[~2007-06-11 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f9be06770706080751y4bbb60d0q3a2286d8e2b576f6@mail.gmail.com>
2007-06-08 14:53 ` Kernel BUG when using corrupted ext3 fs Karl Pickett
2007-06-11 11:41 ` Jan Kara
2007-06-11 14:05 ` Karl Pickett
2007-06-11 20:04 ` Eric Sandeen [this message]
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=466DAAD9.2030207@sandeen.net \
--to=sandeen@sandeen.net \
--cc=karl.pickett@gmail.com \
--cc=linux-kernel@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 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.