From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] migrate luks key-slots to another luks container
Date: Wed, 16 Jan 2013 22:54:02 +0100 [thread overview]
Message-ID: <20130116215401.GA10544@tansi.org> (raw)
In-Reply-To: <50F71BBB.2030603@strike.wu.ac.at>
On Wed, Jan 16, 2013 at 10:29:31PM +0100, Alexander 'Leo' Bergolth wrote:
> Am 16.01.2013 22:08, schrieb Arno Wagner:
> >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?
As Milan said, no.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
prev parent reply other threads:[~2013-01-16 21:54 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
2013-01-16 21:54 ` Arno Wagner [this message]
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=20130116215401.GA10544@tansi.org \
--to=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