Linux LVM users
 help / color / mirror / Atom feed
From: Xen <list@xenhideout.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Copying a raw disk image to LVM2
Date: Mon, 11 Jul 2016 09:32:12 +0200	[thread overview]
Message-ID: <de4e7a649085f2de3c96d4c3113bade9@dds.nl> (raw)
In-Reply-To: <CAE7pJ3ARBWgFmuHKCm+pMO+K2=20bcps6P-T_RL7-rwbEgHKKQ@mail.gmail.com>

emmanuel segura schreef op 11-07-2016 0:02:

> the lvm metadata is stored in the begining of the physical volume, the
> logical volume is simple block device, so using dd you don't overwrite
> any lvm header.

I must say I did experience something weird when copying a LUKS 
partition (encrypted).

Apparently LUKS stores information about the device it is on (or was 
one) because I coudln't get it to re-adjust to a larger volume.

cryptsetup resize is supposed to resize to the size of the underlying 
block device.

I had to recreate my LUKS container before it would recognise the new 
size.

E.g. I copied from 2GB volume to 3GB volume using dd.

LUKS kept thinking it was still on a 2GB volume.

So resize didn't work and I could manually resize it to 3GB but 
automatic resize would resize it back to 2GB.

      reply	other threads:[~2016-07-11  7:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-08 15:52 [linux-lvm] Copying a raw disk image to LVM2 Brian McCullough
2016-07-09 12:23 ` Марк Коренберг
2016-07-09 17:00 ` Digimer
2016-07-09 17:33   ` Марк Коренберг
2016-07-09 20:25     ` Brian McCullough
2016-07-10 22:02     ` emmanuel segura
2016-07-11  7:32       ` Xen [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=de4e7a649085f2de3c96d4c3113bade9@dds.nl \
    --to=list@xenhideout.nl \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox