From: Ondrej Kozina <okozina@redhat.com>
To: Ingo Franzki <ifranzki@linux.ibm.com>, dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2
Date: Thu, 2 Aug 2018 11:20:01 +0200 [thread overview]
Message-ID: <e4f30bb0-7e83-e93b-8178-964b2ab40004@redhat.com> (raw)
In-Reply-To: <6df9d673-5392-1171-3cd7-ed8a244b565e@linux.ibm.com>
On 08/02/2018 10:16 AM, Ingo Franzki wrote:
> Hi,
>
> I have converted an existing LUKS1 volume to LUKS2 via 'cryptsetup convert --type luks2 <device>'.
> That worked well.
>
> After that I am trying to use cryptsetup-reencrypt ro reencrypt the volume using a different volume key.
> This fails with 'Cannot format device LUKS-5d6495ba-b6f9-43c5-883f-dff56f10c72a.new.'
Ok, I know what's wrong. The convert action works as expected and
there's nothing wrong with data offset. The issue is
cryptsetup-reencrypt utility currently can't handle setup where existing
LUKS2 header, on a device you're about to reencrypt is different size
from default LUKS2 header size which is 4MiBs currently. The converted
header is as you wrote 2MiBs.
Ondrej
next prev parent reply other threads:[~2018-08-02 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 8:16 [dm-crypt] cryptsetup-reencrypt fails after converting a LUKS1 volume to LUKS2 Ingo Franzki
2018-08-02 8:52 ` Ondrej Kozina
2018-08-02 9:20 ` Ondrej Kozina [this message]
2018-08-02 9:28 ` Michael Kjörling
2018-08-02 9:44 ` Ondrej Kozina
2018-08-02 10:38 ` Ingo Franzki
2018-08-02 10:56 ` Ondrej Kozina
2018-08-02 13:05 ` Ondrej Kozina
2018-08-02 13:42 ` Ingo Franzki
2018-08-02 14:24 ` Ondrej Kozina
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=e4f30bb0-7e83-e93b-8178-964b2ab40004@redhat.com \
--to=okozina@redhat.com \
--cc=dm-crypt@saout.de \
--cc=ifranzki@linux.ibm.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.