From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] creating DD copies of disks
Date: Sat, 17 Sep 2016 15:49:36 +0200 [thread overview]
Message-ID: <20160917134936.GF3302@soda.linbit> (raw)
In-Reply-To: <7e54ddf6638609d4e521287b51964ebd@dds.nl>
On Sat, Sep 17, 2016 at 09:29:16AM +0200, Xen wrote:
> I want to ask again:
>
> What is the proper procedure when duplicating a disk with DD?
depends on what you define as "proper",
what the desired outcome is supposed to look like.
What exactly are you trying to do?
If you intend to "clone" PVs of some LVM2 VG,
and want to be able to activate that on the same system
without first deactivating the "original",
I suggest:
1) create consistent snapshot(s) or clone(s) of all PVs
2) import them with "vgimportclone",
which is a shell script usually in /sbin/vgimportclone,
that will do all the neccessary magic for you,
creating new "uuid"s and renaming the vg(s).
> - my experience indicates that pvchange -ay on a PV that contains a
> duplicate VG, even if it has a different UUID, but with an identical name,
> creates problems.
You don't say...
--
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support
DRBD� and LINBIT� are registered trademarks of LINBIT
next prev parent reply other threads:[~2016-09-17 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-17 7:29 [linux-lvm] creating DD copies of disks Xen
2016-09-17 13:49 ` Lars Ellenberg [this message]
2016-09-17 14:40 ` Xen
2016-09-17 18:02 ` Lars Ellenberg
2016-09-20 8:04 ` Zdenek Kabelac
[not found] <368387847.156920.1474117496841.ref@mail.yahoo.com>
2016-09-17 13:04 ` matthew patton
2016-09-17 14:16 ` Xen
2016-09-17 14:53 ` Xen
2016-09-17 15:18 ` Michael D. Setzer II
2016-09-17 15:40 ` Xen
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=20160917134936.GF3302@soda.linbit \
--to=lars.ellenberg@linbit.com \
--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 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.