Linux LVM users
 help / color / mirror / Atom feed
From: Rich Turner <rich@storix.com>
To: linux-lvm@sistina.com
Subject: [linux-lvm] create vg with same name as exported vg
Date: Wed Oct  1 18:15:02 2003	[thread overview]
Message-ID: <1065050019.1267.20.camel@rich> (raw)

i have run into a situation where lvm2 does not behave the same as lvm1.
basically i want to be able to create a vg with the same name as an
exported vg.

in lvm1 (v1.0.3) is was able to export the vg and create a vg with the
same name on a different pv. the original "vgturner4" was on /dev/hda6.
# vgchange -a n vgturner4
# vgexport vgturner4
# pvcreate -ff /dev/hda7
# vgcreate vgturner4 /dev/hda7

in lvm2 (v2.00.07) it complained that there was already a vg with that
name. the original vg was on /dev/sdc.
# vgchange -a n vg1
# vgexport vg1
# pvcreate -ff /dev/sda
# vgcreate vg1 /dev/sda
  A volume group called 'vg1' already exists.

a "vgscan" in lvm1 returns:
# vgscan
vgscan -- reading all physical volumes (this may take a while...)
vgscan -- found active volume group "vg0"
vgscan -- found active volume group "vgturner4"
vgscan -- found active volume group "vg0m"
vgscan -- found exported volume group "vgturner4PV_EXP"
vgscan -- "/etc/lvmtab" and "/etc/lvmtab.d" successfully created
vgscan -- WARNING: This program does not do a VGDA backup of your volume
groups

a "vgscan" in lvm2 returns:
# vgscan
Reading all physical volumes.  This may take a while...
  Found exported volume group "vg1" using metadata type lvm2

i notice that the exported vg in lvm1 is actually renamed but in lvm2 it
retains its original name. any ideas on how to accomplish what i want to
do in lvm2?

rich turner

             reply	other threads:[~2003-10-01 18:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-01 18:15 Rich Turner [this message]
2003-10-02 15:34 ` [linux-lvm] create vg with same name as exported vg Rich Turner
2003-10-10 14:03   ` Alasdair G Kergon
2003-10-10 14:22     ` Rich Turner
2003-10-10 14:42       ` Alasdair G Kergon

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=1065050019.1267.20.camel@rich \
    --to=rich@storix.com \
    --cc=linux-lvm@sistina.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