From: Tod <tod@stthomasepc.org>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Renaming Loopback 'Mounted' Volume Group
Date: Fri, 23 Nov 2007 16:35:12 -0500 [thread overview]
Message-ID: <47474790.9010009@stthomasepc.org> (raw)
Please take a look at this old thread first ...
http://linux.derkeiler.com/Mailing-Lists/Fedora/2007-02/msg02237.html
This was back in February and I'm just now trying to get back into
recovery mode. I've mounted the image like so:
/sbin/losetup /dev/loop0 ./recover.img
/sbin/kpartx -lv /dev/loop0
/sbin/kpartx -av /dev/loop0
This gives me /dev/mapper/loop0p1, and /dev/mapper/loop0p2 which seem to
be my original boot drive and VolGroup00. When I do an lvscan I get:
WARNING: Duplicate VG name VolGroup00: Existing
Vmi02d-0hr7-7NVb-vYZi-1fbD-E9n5-ixWu0a (created here) takes precedence
over D7avZX-pVCb-ibTN-tyvs-7Q62-rzR9-tquBi9
Presumably the latter is the UUID of the volume group on my disk image.
Is there a way that I can now rename this original volume group so it
doesn't conflict with my currently mounted one so I can start the data
recovery process? I tried vgrename, which I thought could use UUID's as
input, but that didn't work. Any ideas?
FC6
lvm2-2.02.17-1.fc6
Thanks - Tod
next reply other threads:[~2007-11-23 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 21:35 Tod [this message]
2007-11-26 8:28 ` [linux-lvm] Renaming Loopback 'Mounted' Volume Group Bryn M. Reeves
2007-11-27 2:58 ` Tod
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=47474790.9010009@stthomasepc.org \
--to=tod@stthomasepc.org \
--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.