Hello,

I've encoutered the following strangeness with a newly installed box.
This box was not previously running Linux, but has been carefully tested
with memtest86, cpuburn, and some smalls scripts of mine. So hardware
failure may be excluded at first.

The box is an asus a7m266D with dual athlon-MP (true MP), 2Go RAM, and
the raid 5 set is build on 4 maxtor 160Go connected to 2 additionals
sil0680 ata133 IDE controllers.

I use dm aes encryption over sotfware raid5, and under heavy load,
I get theses error messages, and the partition is remounted ro:

8<--
EXT3-fs error (device dm-6): ext3_readdir: bad entry in directory
#20515395: rec_len % 4 != 0 - offset=0, inode=1605429031, rec_len=14026,
name_len=177
Aborting journal on device dm-6.
ext3_abort called.
EXT3-fs error (device dm-6): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device dm-6) in start_transaction: Journal has aborted
(repeated 3 times)
EXT3-fs error (device dm-6) in ext3_ordered_writepage: IO failure
EXT3-fs error (device dm-6) in start_transaction: Journal has aborted
(repeated 53 times)
__journal_remove_journal_head: freeing b_committed_data (repeated 5 times)
-->8

It is easily reproducible.

fsck show no error, no hardware related message found in dmesg, the raid
set is not marked as bad, no reconstruction needed. I just remount the
partition rw, and now try to keep the box out of pressure.

Googling around I found theses threads, but it does not contain a
conclusion:
http://marc.theaimsgroup.com/?l=linux-kernel&m=107913912311421&w=2
and
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+295657

The kernel is patched with grsec, I have disabled it all but same
behaviour occur, maybe a vanilla will change something, but previous
links show same error on non-grsec kernel.

attached is my .config and boot-time dmesg.