From: malahal@us.ibm.com
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] Mounting an LVM disk image.
Date: Mon, 18 Jan 2010 19:32:12 -0800 [thread overview]
Message-ID: <20100119033212.GA18351@us.ibm.com> (raw)
In-Reply-To: <42784f261001181815y340170dbs4775230080358bc3@mail.gmail.com>
Jason Dusek [jason.dusek@gmail.com] wrote:
> I'm trying to mount a disk image that contains an LVM volume.
> I've managed to follow this tutorial to the point where I've
> got the volume on `/dev/loop7':
>
> http://www.thegibson.org/blog/archives/467
>
> Now I want to mount the image. My machine, a CentOS machine,
> is already using LVM; running `lvm pvscan' shows me that the
> the disk image has been stuck in `VolGroup00' with the rest of
> them:
>
> :; lvm pvscan
> PV /dev/loop7 VG VolGroup00 lvm2 [7.88 GB / 0 free]
> PV /dev/sda5 VG VolGroup00 lvm2 [133.06 GB / 0 free]
> PV /dev/sdb2 VG VolGroup00 lvm2 [135.16 GB / 0 free]
> Total: 3 [276.09 GB] / in use: 3 [276.09 GB] / in no VG: 0 [0 ]
Looks like a name clash here. You have a volume group names VolGroup00
with two PVs (sda5 and sdb2 in it). /dev/loop7 is also a PV with same
group name VolGroup00. They should have different UUIDs though...
You may be running into this problem:
http://liorkaplan.wordpress.com/2008/07/25/when-lvm-volume-groups-collide/
And this method may work, although written for something else:
http://thread.gmane.org/gmane.linux.lvm.general/9628
It is probably a lot easier to with a system that doesn't have
VolGroup00 to begin with!
> At this point in the tutorial, I run in to trouble. As they
> suggest, I run `lvm vgchange -ay' and then inspect
> `/dev/mapper':
>
> :; lvm vgchange -ay
> 2 logical volume(s) in volume group "VolGroup00" now active
> 2 logical volume(s) in volume group "VolGroup00" now active
> :; ls /dev/mapper/
> control VolGroup00-LogVol00 VolGroup00-LogVol01
>
> Mounting fails:
>
> :; mount -t ext2 /dev/mapper/VolGroup00-LogVol01 /media/img/
> mount: /dev/mapper/VolGroup00-LogVol01 already mounted or /media/img/ busy
> :; mount -t ext2 /dev/mapper/VolGroup00-LogVol00 /media/img/
> mount: /dev/mapper/VolGroup00-LogVol00 already mounted or /media/img/ busy
> mount: according to mtab, /dev/mapper/VolGroup00-LogVol00 is mounted on /
You are probably trying to re-mount the root device and swap devices.
> At this point, I'm stuck. I've tried removing `/dev/loop7'
> from the volume group, to no avail:
>
> :; vgcreate shim /dev/loop7
> Physical volume '/dev/loop7' is already in volume group 'VolGroup00'
> Unable to add physical volume '/dev/loop7' to volume group 'shim'.
> :; vgreduce VolGroup00 /dev/loop7
> Physical Volume "/dev/loop7" not found in Volume Group "VolGroup00"
Again, this is probably an artifact of name space collision!
> What's the right way to mount and LVM disk image? I'm doing it
> to perform maintenance on a Xen guest.
Certainly easier to work on a system that doesn't have VolGroup00 to
begin with. If you can't avoid it, you may try renaming the volume group
using uuid or the above mentioned link that is written for cloning a
volume group.
Thanks, Malahal.
next prev parent reply other threads:[~2010-01-19 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 2:15 [linux-lvm] Mounting an LVM disk image Jason Dusek
2010-01-19 3:01 ` J Nb
2010-01-19 3:32 ` malahal [this message]
2010-01-19 18:51 ` Jason Dusek
2010-01-19 19:34 ` Stuart D. Gathman
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=20100119033212.GA18351@us.ibm.com \
--to=malahal@us.ibm.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.