linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] separate vg create, or merge?
Date: Mon, 23 May 2016 10:33:11 +0200	[thread overview]
Message-ID: <b4b9104b-2755-71d1-333e-c097721274dc@redhat.com> (raw)
In-Reply-To: <1953f85f68fef3b30d5efeef85aec94d@dds.nl>

On 21.5.2016 17:38, Xen wrote:
> If I can ask.
>
> Can you separately create two PVs, put a VG to them, and fill them with LVs,
> when these VGs would have the same name, and then at some later point, in that
> sense, you would combine them?
>
> I guess in practice if that happens you would have the ability to just use
> vgextend.
>
> But what if you allowed two pre-existing PVs/VGs when the VGs had the same
> name, in the same system? I believe it wouldn't work very well?
>
> Currently I just gave them different names and plan on merging them.


Hi

Not sure what's your concern this time - however are not allowed to 'create' 
same VG for 2nd. time in running system (vgname is name of lock)

If you happen to do a  'dd'  copy -  lvm2 will loudly announce duplicate 
device and will either stop processing and tell user which device it has 
selected to use.

If you insist on having same 'VG' in one system - you have to use 'filter'
to select which devices individual commands may use  (typically you have
a 'Host' system with number of  'Guesses' and you want to 'sneak view' what's 
in the guest disk - so you run 'lvm2' command with filter to only see a single 
disk.


vgsplit & vgmerge have their validation.

vgrename  allows you to rename VG if they have same name but different UUID.

and finaly -

use 'vgimportclone'  utility when you do a PV device duplication...


Regards

Zdenek

      reply	other threads:[~2016-05-23  8:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-21 15:38 [linux-lvm] separate vg create, or merge? Xen
2016-05-23  8:33 ` Zdenek Kabelac [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=b4b9104b-2755-71d1-333e-c097721274dc@redhat.com \
    --to=zkabelac@redhat.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 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).