From: Milan Broz <mbroz@redhat.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>
Cc: linux-kernel@vger.kernel.org, dm-crypt@saout.de
Subject: Re: data corruption with dmcrypt/LUKS
Date: Mon, 04 Feb 2008 10:17:00 +0100 [thread overview]
Message-ID: <47A6D80C.9070204@redhat.com> (raw)
In-Reply-To: <1202085829.3223.19.camel@fermat.scientia.net>
Christoph Anton Mitterer wrote:
> On Sun, 2008-02-03 at 23:06 +0100, Milan Broz wrote:
...
>>> 2) The second bug happens only rarely and leads to a panic.
>>> Unfortunately it's difficult to reproduce, but it always happened when I
>>> mkfs.ext3 on the /dev/mapper/sda2.
>>> There's a stack-trace printed which clearly involves some dmcrypt
>>> lines...
>> But no stack trace attached here... please attach it.
> Unfortunately I don't have one,... nothing was written to the logs and I
> forgot to write it up :-/
>
>
>
>> It can be known bug which was fixed in stable version some time ago
>> see http://lkml.org/lkml/2007/7/20/211
> Uhm but that patch should be part of 2.6.24, shouldn't it?
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).
...
> btw: What's about the dmcrypt mailing list,.. I've tried to subscribe
> but no answers, and I get not posts (not even my owns).
This is another story...
I hope that someone with admin rights will fix it (Christophe ?)
Milan
--
mbroz@redhat.com
next prev parent reply other threads:[~2008-02-04 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 14:50 data corruption with dmcrypt/LUKS 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 [this message]
2008-02-05 1:28 ` Christoph Anton Mitterer
[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=47A6D80C.9070204@redhat.com \
--to=mbroz@redhat.com \
--cc=calestyo@scientia.net \
--cc=dm-crypt@saout.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.