Bug#336153: Reproduced, also using ext2 + dm-crypt on top of RAID5
Hello,
I managed to reproduce the bug using a newer kernel (actually, I didn't
_try_ to reproduce it, I ran into it and a google search brought up this
bug, which occured under almost identical circumstances).
My configuration is very similar to that of the original submitter; I
also use dm-crypt with AES on top of a 4x160GB RAID5 system, and the
problem also occurs when copying large amounts of data on the ext2
partition.
There might possibly be an issue with ext2 on RAID5+dm-crypt. After
reboot, the ext2 filesystem is erronous, and the above message appears
even when reading it.
I have previously used the same encrypted volume with Reiser4, and there
were no problems whatsoever (despite Reiser4 being experimental and ext2
super-stable :)). I also trust my hardware very much; this server has
been super stable for many months. SMART status of the disks is also OK.
Unfortunately, I don't use a debian-supplied kernel; I use a
selfcompiled 2.6.13 with archck patchset (2.6.13-archck2). The rest of
the system, including the ext2 tools, is a standard sarge system.
I am now switching the partition to ReiserFS 3.6 and will do further
tests. In the unlikely case that there will still be problems when not
using ext2, I will report back.
bye,
Tillmann
Reply to: