From: "Dan Merillat" <harik.attar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [dm-crypt] dm-crypt is broken and causes massive data corruption
Date: Fri, 12 May 2006 17:47:06 -0400 [thread overview]
Message-ID: <c0c067900605121447k35bacaffwc3feca071385ca6a@mail.gmail.com> (raw)
In-Reply-To: <e3vkeh$12h$1@news.cistron.nl>
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.
prev parent reply other threads:[~2006-05-12 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 17:20 Tillmann Steinbrecher
2006-05-08 17:57 ` [dm-crypt] " Simpson, Brett
2006-05-08 18:27 ` Christophe Saout
2006-05-09 19:04 ` Alasdair G Kergon
2006-05-11 15:15 ` Paul Slootman
2006-05-11 15:42 ` Andrea Gelmini
2006-05-11 23:17 ` Christian Schmidt
2006-05-12 21:47 ` Dan Merillat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0c067900605121447k35bacaffwc3feca071385ca6a@mail.gmail.com \
--to=harik.attar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®