From: Xen <list@xenhideout.nl>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] export/migrate - but only a LV - how?
Date: Fri, 22 Jul 2016 15:49:49 +0200 [thread overview]
Message-ID: <8d8a6f9b8f6a621c29e80b853f6c5839@dds.nl> (raw)
In-Reply-To: <5C234A9A-A73D-4E4E-ABD9-1ADCEF255333@redhat.com>
Brassow Jonathan schreef op 22-07-2016 15:12:
> One advantage is that pvmove allows you to keep the device online...
Right, that is pretty advanced. Good going.
> We are also working on a feature ATM called “duplicate”. It allows
> you to create a duplicate of any LV stack, create the duplicate where
> you want, and even change the segment type in the process. For
> example, you could move a whole RAID5 LV, or thin-p, in one go.
I think one important "trouble spot" is that there is no operation
yet(?) to create a duplicate of a PV that will not ruin the system
unless you do pvchange -u and vgchange -u ;-).
It took quite a bit of time for me to realize what was going on ;-).
Is PVMOVE supposed to be a backup task? I don't think so? How are you
supposed to back something up if you are planning to move your system to
a new disk?
prev parent reply other threads:[~2016-07-22 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 15:23 [linux-lvm] export/migrate - but only a LV - how? lejeczek
2016-07-18 15:50 ` Brassow Jonathan
2016-07-18 20:28 ` Xen
2016-07-22 13:12 ` Brassow Jonathan
2016-07-22 13:49 ` 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=8d8a6f9b8f6a621c29e80b853f6c5839@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;
as well as URLs for NNTP newsgroup(s).