Re: [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit

From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid	64bit
Date: Fri, 3 Sep 2010 20:14:29 +0200	[thread overview]
Message-ID: <20100903181429.GA11768@tansi.org> (raw)
In-Reply-To: <AANLkTi=5PpL55_nykfZ8Pcq7UBNAOKtEGc7in7ZBG==x@mail.gmail.com>

I would recomend one read-thrugh of the FAQ. Just posted it today
and it is also in the web here:
  http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions

The most important thing to know is that if you trash the LUKS
header, you are screwed ;-)

Arno

On Fri, Sep 03, 2010 at 04:12:25PM +0200, Thorsten Peter wrote:
> Sorry man, sent one of my msgs using a false E-Mail address, please reply to
> my other address if possible: boba23@gmail.com. That's the one that is
> registered in the list.
> 
> thx
> 
> Thorsten
> 
> On Fri, Sep 3, 2010 at 4:10 PM, Thorsten Peter <
> thorsten.peter@googlemail.com> wrote:
> 
> > Hey Milan,
> >
> > could you give me a pointer on how to setup the encryption using LUKS? I am
> > totally new to dm-crypt. Just used the first method that I found in the
> > howto ....
> > Right now I am following Ricks advice and upgrading to 2.6.35 from a ppa
> > repo.
> >
> > Thanks,
> >
> > Thorsten
> >
> >
> > On Fri, Sep 3, 2010 at 3:57 PM, Milan Broz <mbroz@redhat.com> wrote:
> >
> >> 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
> >>
> >>
> >
> >
> > --
> > --------------------------------
> > Dipl.-Inf. (FH) Thorsten Peter
> >
> > E-Mail: Thorsten.Peter@gmail.com
> > Mobile: 01795322057
> > --------------------------------
> >
> 
> 
> 
> -- 
> --------------------------------
> Dipl.-Inf. (FH) Thorsten Peter
> 
> E-Mail: Thorsten.Peter@gmail.com
> Mobile: 01795322057
> --------------------------------

> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 