Finally ext4 ...or not?

I bought a new HDD and set up RAID 1 with LVM and ext4. (I made it using mkfs.ext4) I was just about to rm my backups I stored on my other disks when rsync failed and I wasn't able to access my new partition anymore. Everything threw I/O Errors.
I wanted to run fsck, but I told me the disk was in use (it wasn't). Couldn't figure out what was the problem so I rebooted and got an error, telling that mount can't mount the partition because it's not ext4 (as I specified in /etc/fstab).
Well I started fsck.ext4 and it threw quite a lot of errors and after some time it started to loop.

Restarting e2fsck from the beginning...
/dev/mapper/VolGroup00-data contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory.  Clear? yes

Inode 5 has illegal block(s).  Clear? yes

Illegal block #12738657 (1613830228) in inode 5.  CLEARED.
Illegal block #12738658 (3211906433) in inode 5.  CLEARED.
Illegal block #12738659 (478689490) in inode 5.  CLEARED.
Illegal block #12738660 (3876020224) in inode 5.  CLEARED.
Illegal block #12738661 (1007945148) in inode 5.  CLEARED.
Illegal block #12738662 (1205590462) in inode 5.  CLEARED.
Illegal block #12738663 (3567108197) in inode 5.  CLEARED.
Illegal block #12738664 (3575479245) in inode 5.  CLEARED.
Illegal block #12738665 (2383729051) in inode 5.  CLEARED.
Illegal block #12738666 (619555458) in inode 5.  CLEARED.
Illegal block #12738667 (3902957544) in inode 5.  CLEARED.
Too many illegal blocks in inode 5.
Clear inode? yes

Restarting e2fsck from the beginning...
/dev/mapper/VolGroup00-data contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Root inode is not a directory.  Clear? yes

Inode 5 has illegal block(s).  Clear? yes

Illegal block #12738668 (1246693144) in inode 5.  CLEARED.
Illegal block #12738669 (2312789758) in inode 5.  CLEARED.
Illegal block #12738670 (332492032) in inode 5.  CLEARED.
Illegal block #12738671 (3850324777) in inode 5.  CLEARED.
Illegal block #12738672 (2442788202) in inode 5.  CLEARED.
Illegal block #12738673 (4227858239) in inode 5.  CLEARED.
Illegal block #12738676 (311437445) in inode 5.  CLEARED.
Illegal block #12738677 (4016009761) in inode 5.  CLEARED.
Illegal block #12738678 (3776456913) in inode 5.  CLEARED.
Illegal block #12738679 (528482688) in inode 5.  CLEARED.
Illegal block #12738680 (1343549598) in inode 5.  CLEARED.
Too many illegal blocks in inode 5.
Clear inode? yes

Now I knew my FS actually died :( I was maybe 3h old.

Here's the command that killed it:
rsync -rvtlpEog --safe-links ~/backup/mistral_backup/ mistral_backup/ --progress

To all ext4 users: Make backups on some different FS! Ext4 is NOT stable!

Update:
The problem could be that I didn't wait for the RAID to finish syncing.

Arch64, OSS and Flash

Some time ago Adobe finally brought the Flashplugin for 64-bit. To get sound working with OSS I had to use the ALSA-wrapper as described here. That worked well for some time, but around 2 or 3 weeks ago flash suddenly stopped working.

Every flash film was damn slow. It felt as if I was running on 100MHz or something. Maybe 1 picture every 5 seconds. Sound was a bit better, but out of sync and stopped sometimes. CPU usage was only 3% and atop nor iotop showed anything suspicious.

I didn't know why because I didn't upgrade anything nor did I change any config file. I googled a bit and asked around, but apparently nobody had a solution.

Then I just ignored that and today I wanted to try if it works again. So I went to youtube, disabled HQTube (A script to play youtube files in mplayer) and started a video. As you can imagine it still didn't work.

I asked the guys in #archlinux.de and we tried some things like adding a new user, using a different Browser, taking out some RAM because strace segfaulted with an error telling that the RAM was bad and finally installing a new system on a different HD.

There I installed everything needed to run Firefox with Flash and guess what. It worked! That meant that my hardware was actually okay so I rebooted the old system and tried to find the cause.

First I thought it might be uvesafb (which still doesn't work with widescreen resolutions). Then I tried using a new xorg.conf without the new fancy HAL stuff and starting X without slim.

Nothing helped and the guys in the IRC didn't have a clue either. But then I remembered that the second system, where flash worked, didn't have any sound. So I disabled OSS and tried again. Worked!! Suddenly I knew what was wrong:
I've set "vmix0-src" to "Production" because I read somewhere that it wouldn't take much CPU, but sound a bit better. Actually it didn't need more when running mplayer, mpd or vlc. Nevertheless I set it back to "Fast" and suddenly flash worked again.

That's really the strangest bug I've ever seen and I have a message for everyone who uses (only) the ALSA API in their programs:

Switch to OSS. It's better:

• OSS wastes less ressources than ALSA.
• OSS is able to let multiple programs use the same soundcard to output sound in parallel. ALSA needs an overlay (which again wastes ressources) to do that.

If you need more see here.

Special Thanks to IGProLin for telling me to install a second system.