Bug#336153: Bug 336153 must be fixed ASAP - filesystem corruption IS critical!
Hi, I can't understand why Bug 336153 still has status pending. It's a well-known issue that causes massive data corruption. It is reproducible and has been confirmed by several people, including the dm-crypt developer himself. A patch has been available for several MONTHS. It's a simple 4-line patch. How come it isn't applied for the etch kernel? It is required for kernel 2.6.18 which is used for etch. It is NOT required for 2.6.19 and future kernels. See also: http://www.spinics.net/lists/dm-crypt/msg00481.html bye, Tillmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#336153: Fixed in kernel 2.6.19, patch for older kernels available
Hi, this is (was) a well known bug in dm-crypt; numerous people have reported it. It was just fixed by Christophe Saout. See http://www.spinics.net/lists/dm-crypt/msg00481.html (message from dm-crypt mailing list) for short description and patch. Debian kernel package maintainers: Please apply this patch for debian kernels. It's really important due to the amount of data that can possibly be lost due to fs corruptions related to this problem. The bug is also fixed in kernel 2.6.19. All the best, Tillmann -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
