From: Mauricio Tavares <raubvogel@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] Conflicting vg names but can't rename one
Date: Fri, 17 Dec 2010 12:27:13 -0500 [thread overview]
Message-ID: <4D0B9D71.3080602@gmail.com> (raw)
I took a drive from an ailing machine to suck the data out of it. This
drive used to be part of a single drive LVM. Now, when I connect it to
my machine, I realized I had named that vg the same name I had used in
the vg I have in my desktop associated with just one drive,
vgdisplay export
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
--- Volume group ---
VG Name export
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 2
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 1
Act PV 1
VG Size 465.76 GiB
PE Size 4.00 MiB
Total PE 119234
Alloc PE / Size 102400 / 400.00 GiB
Free PE / Size 16834 / 65.76 GiB
VG UUID fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB
We see that UUID fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB is the drive/vg
in use while UUID SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D is the extra
drive I just attached to my machine. So I thought on using vgrename to
change the name of the extra drive's vg so I can mount it:
vgrename SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D export1
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
WARNING: Duplicate VG name export: Existing
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
WARNING: Duplicate VG name export:
fjM9qy-aCEM-iluj-yTdQ-CwT5-Iijk-uOYXlB (created here) takes precedence
over SB3NfW-swQM-5rdw-xf5e-z6At-r5DM-dUwG7D
Volume group "export" still has active LVs
What am I missing here? I thought if I told it to rename the vg with a
given uuid I would be golden. As you can see, that is not the case.
next reply other threads:[~2010-12-17 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 17:27 Mauricio Tavares [this message]
2010-12-17 18:46 ` [linux-lvm] Conflicting vg names but can't rename one Alasdair G Kergon
2010-12-17 19:38 ` Mauricio Tavares
2010-12-17 18:56 ` Richard Shaw
2010-12-17 20:29 ` Mauricio Tavares
2010-12-17 21:11 ` Stuart D Gathman
2010-12-17 21:37 ` Richard Shaw
2010-12-17 21:37 ` chris procter
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=4D0B9D71.3080602@gmail.com \
--to=raubvogel@gmail.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.