From: Andrea Gelmini <andrea.gelmini@gmail.com>
To: Paul Slootman <paul+nospam@wurtel.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [dm-crypt] dm-crypt is broken and causes massive data corruption
Date: Thu, 11 May 2006 17:42:41 +0200 [thread overview]
Message-ID: <20060511154241.GA5959@gelma.net> (raw)
In-Reply-To: <e3vkeh$12h$1@news.cistron.nl>
On Thu, May 11, 2006 at 03:15:29PM +0000, Paul Slootman 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...).
It seems the write pattern is important... I can replicate corruption
copying giga of data from an locale attached IDE disk. Do you write mostly
from network or from slow devices?
ciao,
gelma
next prev parent reply other threads:[~2006-05-12 15:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-08 17:20 dm-crypt is broken and causes massive data corruption 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 [this message]
2006-05-11 23:17 ` Christian Schmidt
2006-05-12 21:47 ` Dan Merillat
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=20060511154241.GA5959@gelma.net \
--to=andrea.gelmini@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul+nospam@wurtel.net \
/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