From: Milan Broz <mbroz@redhat.com>
To: Thorsten Peter <thorsten.peter@googlemail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit
Date: Fri, 03 Sep 2010 15:57:59 +0200 [thread overview]
Message-ID: <4C80FEE7.3030508@redhat.com> (raw)
In-Reply-To: <4C80F647.9080500@gmail.com>
On 09/03/2010 03:21 PM, Thorsten Peter wrote:
> I am switching from loop-aes to dm_crypt. I am trying to use it on a
> fresh Ubuntu 64bit server installation with my 6x750gb Software raid5 array.
> Array is clean and freshly created, I encrypted it using
>
> cryptsetup -y -c aes -h ripemd160 -s 256 create STUFF /dev/md0
Please use LUKS instead here to get persistent header.
> Format went fine, but when I try to copy back large amount of data to
> the encrypted array (about 900gig) my copy thread always hangs itself at
> some point during the process. I can't access the array anymore, though
> the raid itself is fine, no drives are kicked out or anything.
> Reboot gives me back access and the array is still ok.
> When the problem occures I see the following trace in log:
>
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] Pid: 400, comm:
> md0_raid5 Not tainted 2.6.32-24-server #41-Ubuntu Unknow
If it is reproducible with upstream kernel, please send me OOPs,
if not, please use Ubuntu bugzilla - I saw strange reports which were never
reproducible on upstream.
(The bug seems like something we fixed long time ago.)
Milan
next prev parent reply other threads:[~2010-09-03 13:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 13:21 [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit Thorsten Peter
2010-09-03 13:57 ` Milan Broz [this message]
2010-09-03 14:10 ` Thorsten Peter
2010-09-03 14:12 ` Thorsten Peter
2010-09-03 18:14 ` Arno Wagner
2010-09-04 11:14 ` Thorsten Peter
2010-09-05 12:34 ` BOBA FETT
2010-09-05 12:56 ` Arno Wagner
2010-09-05 16:42 ` Milan Broz
2010-09-06 3:40 ` Arno Wagner
2010-09-06 6:25 ` Heinz Diehl
2010-09-03 13:22 BOBA FETT
2010-09-03 13:36 ` Rick Moritz
2010-09-03 13:52 ` BOBA FETT
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=4C80FEE7.3030508@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=thorsten.peter@googlemail.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 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.