Skip to contentSkip to conversation

+ EXT4 corruption

2.6.32-rc4 Shawn Starr 3 participants 4 messages Oct 13, 2009

lore
Share & tools
lore
#0 lore 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.

#1 lore raw
Quoted 19 lines · Shawn Starr

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.

Quoted 2 lines

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

#2 lore raw
Quoted 20 lines · Theodore Tso
Quoted 19 lines · Shawn Starr

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.

Quoted 8 lines
Quoted 2 lines

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?

I triggered what might have been the same bug awhile ago on 2.6.32-rc2 or so (with your patch to fix a writepages OOPS applied, I think). I crashed my system by doing something dumb with the i915 driver, and, after power cycling, I had all kinds of corrupt inodes. e2fsck fixed it
just fine and only lost /etc/ld.so.cache.

This was LVM over dm-crypt on a partition on AHCI on a real (non-SSD) hard disk.

--Andy

Quoted 5 lines

- Ted

#3 lore raw
In reply to Theodore Tso
Quoted 23 lines · Theodore Tso
Quoted 19 lines · Shawn Starr

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.

Quoted 2 lines

I'm guessing no matter how much you attempt to replay a journal you still can get corruption such as this?

Quoted 8 lines

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

Hi Ted,

No LVM, no encryption. Regular primary partitions. root is on sda4, swap on sda3, /boot is on sda2, sda1 contains another OS that came with laptop.

/ is mounted as:
/dev/sda4 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro)

Some more information:

I was in X with several KDE and non-KDE applications at the time of the swap storm. I noticed in my .viminfo file contents got corrupted with of some .kde4 configurations (looks to be a plasma configuration), lost my kconversationrc completely. That file is was also in $HOME/.kde4/config.

fsck.ext4 asked me if I wanted to clone some inodes and truncate illegal ones. I said yes to all the warnings (too bad it doesn't have a log of that anywhere I could give you).

It might be useful to have fsck write a log file to filesystem after its cleaned, then one could provide you a full dump of what fsck says and what EXT4 spits out?

I am pretty sure I can reproduce the corruption. I am more surprised that opened files such as .viminfo were corrupted when they are not being changed? (I don't believe vim examines the file if you've loaded it once during start of vim?)

Thanks,
Shawn.