DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander 'Leo' Bergolth <leo@strike.wu.ac.at>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 22:29:31 +0100	[thread overview]
Message-ID: <50F71BBB.2030603@strike.wu.ac.at> (raw)
In-Reply-To: <20130116210840.GA10215@tansi.org>

Am 16.01.2013 22:08, schrieb Arno Wagner:
> On Wed, Jan 16, 2013 at 09:51:36PM +0100, Alexander 'Leo' Bergolth wrote:
>> Am 16.01.2013 21:14, schrieb Arno Wagner:
>>> Any reason why you want to change the cipher? After all, you can
>>> not enlarge the key and keep the keyslots.
>>>
>>> As to size, just enlarge the partition. Offset, I don't know,
>>> but if you do not need to keep any data, just changing the
>>> repective fiels in the header should do it. But is there really
>>> any reason to change the offset?
>>
>> The motivation behind this is because I'd like to migrate the data
>> to another system using a different raid layout.
>> To ensure correct data alignment with the new stripe size, I need to
>> change the payload-offset using --align-payload.
>
> Ah, that makes sense. However, do you actually need this
> alignment? If yor filesystem has, say, 4kB blocks and your
> stripe-size is a multiple of that, it will be aligned anyways.

Unfortunately this isn't easy to achieve if you are using raid5 or 6.
I am moving to a raid6 with 5 disks using 64k chunksize. 64k chunks 
multiplied by the number of data bearing disks (3) results in a stripe 
width of 192k (=384 blocks). Thus I guess I should use 
--align-payload=384. The current setting is different and even the 
default of 1MiB isn't a multiple of that value.

Anyway, is the migration of keyslots possible in my case?

Thanks,
--leo
-- 
e-mail   ::: Leo.Bergolth (at) wu.ac.at
fax      ::: +43-1-31336-906050
location ::: IT-Services | Vienna University of Economics | Austria

  reply	other threads:[~2013-01-16 21:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 18:34 [dm-crypt] migrate luks key-slots to another luks container Alexander 'Leo' Bergolth
2013-01-16 18:50 ` .. ink ..
2013-01-16 19:57   ` Alexander 'Leo' Bergolth
2013-01-16 20:05     ` Milan Broz
2013-01-16 20:14     ` Arno Wagner
2013-01-16 20:19       ` Arno Wagner
2013-01-16 20:33         ` Milan Broz
2013-01-16 20:51       ` Alexander 'Leo' Bergolth
2013-01-16 21:08         ` Arno Wagner
2013-01-16 21:29           ` Alexander 'Leo' Bergolth [this message]
2013-01-16 21:54             ` Arno Wagner

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=50F71BBB.2030603@strike.wu.ac.at \
    --to=leo@strike.wu.ac.at \
    --cc=arno@wagner.name \
    --cc=dm-crypt@saout.de \
    /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