Description:
Hello,

It looks like that since I upgraded to kernel26-2.6.29.2-1 I get some corruption ext3 partitions.

I first reported this problem there: http://bbs.archlinux.org/viewtopic.php?pid=549952
And as it is said in it, this does not look like a disk failure (no badblocks).

This is the errors I got today (for the first time) when some apps stopped working or crashed:
May 9 17:21:35 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 1615043
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks: Freeing blocks in system zones - Block = 33619980, count = 1
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 1542446
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 33689588
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 11822
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 26037022
.
.
.
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 26037141
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 26037142
May 9 18:45:12 goldmund kernel: EXT3-fs error (device sda4): ext3_free_blocks_sb: bit already cleared for block 26037143
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 18:45:34 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 19:49:42 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 19:53:21 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 19:53:21 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0
May 9 19:53:21 goldmund kernel: EXT3-fs error (device sda3): ext3_dx_find_entry: bad entry in directory #1615307: rec_len % 4 != 0 - offset=9408, inode=4278210937, rec_len=20857, name_len=0

I had to repair my system with e2fsck again and I reinstalled kernel26-2.6.28.8-1

Additional info:
* I am on x86_64, I don't know if it is important.