DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: Alberto Gonzalez Iniesta <agi@inittab.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Move from basic dm-crypt to LUKS
Date: Sat, 26 Jun 2010 17:03:08 +0200	[thread overview]
Message-ID: <4C2616AC.8070504@redhat.com> (raw)
In-Reply-To: <20100617170221.GB6305@lib.inittab.org>

On 06/17/2010 07:02 PM, Alberto Gonzalez Iniesta wrote:
> I created a plain dm-crypt mapping on my laptop HD, when (later) I found
> I actually wanted a LUKS one. I know [1] I cannot migrate from
> no-encryption to LUKS (without backup/restore). But can I move my basic
> dm-crypt partition to use LUKS, or am I doomed to backup/restore?

You have to backup/restore. LUKS metadata are located at start of device,
plain dm-crypt have no metadata there. (So the LUKS device will be even smaller
of this metadata area.)

Milan

      reply	other threads:[~2010-06-26 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17 17:02 [dm-crypt] Move from basic dm-crypt to LUKS Alberto Gonzalez Iniesta
2010-06-26 15:03 ` Milan Broz [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=4C2616AC.8070504@redhat.com \
    --to=mbroz@redhat.com \
    --cc=agi@inittab.org \
    --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