All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Expanding a LUKS partition to a second drive.
Date: Wed, 12 Feb 2020 17:48:23 +0100	[thread overview]
Message-ID: <20200212164823.GA29788@tansi.org> (raw)
In-Reply-To: <CAE3N1D+_pZNQGwi8O4dP3c_Hv8PMGkqYHieqTsrfXEi0d1_HGQ@mail.gmail.com>

Hi James,

to be safe, you need to do this with a full backup of the data 
in the LUKS container anyways.
Hence easisest is probably 

backup->make new partition->restore.

The LUKS container itself has no size information, it will 
fill the new parition. For the filesystem, you need to either
backup the LUKS container as ibinary mage and extend the 
filesystem in it after restore, or backup on file-level and 
create a new LUKS container and filesystem in it.

Luks does nto care whther the partition is native or LVM
(or NBD, or whatever).

Regards,
Arno

On Tue, Feb 11, 2020 at 20:21:55 CET, James Dehnert wrote:
>    Greetings dm-crypt group,
>    I have a situation where I have an existing LUKS encrypted partition
>    (root) and the user wants to expand that partition onto a second drive.
>    The existing partition was created at configuration as part of the
>    Ubuntu preseed setup.
>    I know how to do this with LVM, but I'm not sure if this can be done
>    without backing up all the data, and then rebuilding the system from
>    scratch.
>    I'm not sure where the LUKS volume is created in respect to LVM.  I
>    can't tell if its created directly on the physical volume, on the
>    volume group, or on the logical volume, so I'm noy sure where I should
>    be looking to expand the substrate.  Or if this is even possible.
>    Any assistance would be greatly appreciated, even if its just "It can't
>    be done".
>    —
>    Thanks,
    James "Zeke" Dehnert
>      Zeke Dehnert
>      Senior Linux IT Engineer
>      Cruise LLC
>      [1]zeke.dehnert@getcruise.com
> 
>    Confidentiality Note: We care about protecting our proprietary
>    information, confidential material, and trade secrets. This message may
>    contain some or all of those things. Cruise will suffer material harm
>    if anyone other than the intended recipient disseminates or takes any
>    action based on this message. If you have received this message
>    (including any attachments) in error, please delete it immediately and
>    notify the sender promptly.
> 
> References
> 
>    1. mailto:zeke.dehnert@getcruise.com

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


-- 
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
----
A good decision is based on knowledge and not on numbers. -- Plato

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

      parent reply	other threads:[~2020-02-12 16:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-11 19:21 [dm-crypt] Expanding a LUKS partition to a second drive James Dehnert
2020-02-12 10:45 ` Ondrej Kozina
2020-02-12 14:29   ` Robert Nichols
2020-02-12 15:01     ` Ondrej Kozina
2020-02-12 19:15       ` Robert Nichols
2020-02-12 16:48 ` 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=20200212164823.GA29788@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 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.