From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Milan Broz <mbroz@redhat.com>
Cc: linux-kernel@vger.kernel.org, dm-crypt@saout.de
Subject: Re: data corruption with dmcrypt/LUKS
Date: Tue, 05 Feb 2008 02:28:01 +0100 [thread overview]
Message-ID: <1202174881.1070.15.camel@fermat.scientia.net> (raw)
In-Reply-To: <47A6D80C.9070204@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 824 bytes --]
On Mon, 2008-02-04 at 10:17 +0100, Milan Broz wrote:
> Yes, so if you hit this with 2.6.24 too is very important to sent OOps
> log to identify problem (or link to screen snapshot, digital camera
> snapshot or so).
I did about 5 complete tests today and dozens of mkfs.ext3's but I
wasn't able to reproduce any of the two errors... very very strange.
(used the same sequence of commands, with and without using the
USB-stick)...
I'll do some other tests tomorrow because these problems were real and I
cannot believe, that they're simply gone...
And IMHO hardware problems are still very unlikely, or am I wrong?
Anyway,.. is there anybody who made deeper tests of dmcrypt? I mean real
massive tests perhaps with different filesystems and so on?
What are your experiences at Redhat?
Best wishes,
Chris
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5108 bytes --]
next prev parent reply other threads:[~2008-02-05 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 14:50 Christoph Anton Mitterer
2008-02-03 22:06 ` Milan Broz
2008-02-04 0:43 ` Christoph Anton Mitterer
2008-02-04 9:17 ` Milan Broz
2008-02-05 1:28 ` Christoph Anton Mitterer [this message]
[not found] ` <47B3639F.10809@yahoo.it>
2008-02-15 21:25 ` Christoph Anton Mitterer
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=1202174881.1070.15.camel@fermat.scientia.net \
--to=calestyo@scientia.net \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
/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®