Messages in this thread | | | Date | Fri, 12 May 2006 17:47:06 -0400 | From | "Dan Merillat" <> | Subject | Re: [dm-crypt] dm-crypt is broken and causes massive data corruption |
| |
On 5/11/06, Paul Slootman <paul+nospam@wurtel.net> wrote:
> A data point: > > I'm running my /home on reiserfs3 over dm-crypt over lvm over raid5 for > at least a year now, without any problems. Currently running 2.6.13.4 > (that's my "stable" work system...).
Datapoint:
Linux fileserver 2.6.15.6 #1 PREEMPT Wed Mar 8 20:26:55 EST 2006 x86_64 GNU/Linux CONFIG_MD_RAID5=y CONFIG_BLK_DEV_DM=y CONFIG_DM_SNAPSHOT=y CONFIG_CRYPTO_AES_X86_64=y
encrypted logical volume on a raid-5 MD on 4 SATA drives, mounted reiser3.
aes-cbc-plain
It's worked through multiple kernels, and moving from 32 to 64bits. 2.6.11 (64-bit) 2.6.10 (64bit) 2.6.8 (32bit) is the kernel history I have so far. I'm not sure when I switched from cryptoloop to dm-crypt though, at least before may '05.
I'm not running dm-crypt directly on MD, though, the stack is SATA->MD->DM->DM-crypt->reiser3. That may be the difference.
I've got plenty of free space, I could make a ~75gb encrypted partition and run any sort of write pattern test/filesystem you want me to try. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |