From: Alasdair G Kergon <agk@uk.sistina.com>
To: Rich Turner <rich@storix.com>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] create vg with same name as exported vg
Date: Fri Oct 10 14:42:01 2003 [thread overview]
Message-ID: <20031010204113.L6588@uk.sistina.com> (raw)
In-Reply-To: <1065813644.1286.16.camel@rich>; from rich@storix.com on Fri, Oct 10, 2003 at 12:20:44PM -0700
On Fri, Oct 10, 2003 at 12:20:44PM -0700, Rich Turner wrote:
> LVM1 actually handled this very well. With LVM1 it would rename the VG,
> appending "PV_EXP" to the VG name when exporting it.
LVM2 still does that for lvm1-format VGs of course.
And for lvm2-format VGs it simply sets a flag in the metadata
to say it's exported.
No, the issue is that LVM2 is using the not-guaranteed-to-be-unique
VG name internally in places where it ought to be using the unique
VG uuid.
And vgimport should work by VG uuid (in case there are several
exported VGs present all with the same name) and require a new
post-imported name to be specified if there's already a live VG
with the same name.
Alasdair
--
agk@uk.sistina.com
prev parent reply other threads:[~2003-10-10 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 18:15 [linux-lvm] create vg with same name as exported vg Rich Turner
2003-10-02 15:34 ` 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 [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=20031010204113.L6588@uk.sistina.com \
--to=agk@uk.sistina.com \
--cc=linux-lvm@sistina.com \
--cc=rich@storix.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.