[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091013022301.GC2606@mit.edu>
Date: Mon, 12 Oct 2009 22:23:01 -0400
From: Theodore Tso <tytso@....edu>
To: Shawn Starr <shawn.starr@...ers.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [2.6.32-rc4] + EXT4 corruption
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists