From: Shawn Starr <shawn.starr@rogers.com>
To: linux-kernel@vger.kernel.org
Subject: [2.6.32-rc4] + EXT4 corruption
Date: Mon, 12 Oct 2009 22:07:49 -0400 [thread overview]
Message-ID: <200910122207.50140.shawn.starr@rogers.com> (raw)
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?
Thanks,
Shawn.
next reply other threads:[~2009-10-13 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 2:07 Shawn Starr [this message]
2009-10-13 2:23 ` [2.6.32-rc4] + EXT4 corruption Theodore Tso
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=200910122207.50140.shawn.starr@rogers.com \
--to=shawn.starr@rogers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox