From: Theodore Tso <tytso@mit.edu>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6.32-rc4] + EXT4 corruption
Date: Mon, 12 Oct 2009 22:23:01 -0400 [thread overview]
Message-ID: <20091013022301.GC2606@mit.edu> (raw)
In-Reply-To: <200910122207.50140.shawn.starr@rogers.com>
On Mon, Oct 12, 2009 at 10:07:49PM -0400, Shawn Starr wrote:
> Hello everyone,
>
> I somehow managed to corrupt some of my filesystem.
>
> What I did was this:
>
> in /etc/modprobe.d/alsa-base.conf (Kubuntu)
>
> I added:
>
> install snd-aloop /sbin/modprobe snd-aloop
>
> Saved it, then ran, modprobe snd-aloop, the system started spawning
> many copies of modprobe, then machine started going though a swap
> storm, could not reboot safely, hit power button on laptop. When the
> system came back up, EXT4 greeted me with severe errors on some
> opened files. It did repair filesystem however. It corrupted some
> configuration files that were open at the time of the shutdown.
>
> I'm guessing no matter how much you attempt to replay a journal you
> still can get corruption such as this?
You shouldn't get any file system corruption after replaying a
journal. I'm trying to get an easily reproducible test case for this.
Can you give me more information about where your root filesystem is
located. Is it using LVM? dm-crypt? Can you reliably reproducible
the file system corruption?
- Ted
next prev parent reply other threads:[~2009-10-13 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 2:07 [2.6.32-rc4] + EXT4 corruption Shawn Starr
2009-10-13 2:23 ` Theodore Tso [this message]
2009-10-13 13:33 ` Andy Lutomirski
2009-10-13 20:20 ` Shawn Starr
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=20091013022301.GC2606@mit.edu \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox