RE: [SLE] 10.1, LVM2, and inaccessible snapshot-related logical volumes

Anyone?

-----Original Message-----
From: Ian Marlier [mailto:ian.marlier@xxxxxxxxxxxxxxxxxxx]
Sent: Tuesday, June 27, 2006 12:56 AM
To: suse-linux-e@xxxxxxxx
Subject: [SLE] 10.1, LVM2, and inaccessible snapshot-related logical
volumes

So, I'm working on setting up a system that's going to run a series of
Xen
virtual machines.

Each of these virtual machines are going to be basically identical,
with
only slight differences in a specific application for testing.

Rather than duplicate the initial setup in whole, I created it as a
logical
volume, and created a second as a snapshot of the first, with a couple
of
gigs of wiggle room.

These partitions, at the time of creation, were addressable as
/dev/xen/vm1
and /dev/xen/vm2 (alternately, /dev/mapper/xen-vm1 and
/dev/mapper/xen-
vm2).

However, after doing a reboot of the host machine, the partitions are
no
longer addressable via the /dev/<vol group name>/<logical volume name>
syntax. They're only available as /dev/dm-1 and /dev/dm-2

`ls -altr /dev/xen/` shows that the device files for vm1 and vm2 do
not
exist. The device files for my other logical volumes, which are not
snapshots, do exist.

Doing `lvscan` shows this:
ACTIVE '/dev/xen/vm0' [20.00 GB] inherit
inactive Original '/dev/xen/vm1' [20.00 GB] inherit
inactive Snapshot '/dev/xen/vm2' [2.90 GB] inherit
ACTIVE '/dev/xen/vm3' [20.00 GB] inherit

So, I'm assuming that the "inactive" state is somehow related to the
device
files being missing; and that the inactive state is somehow related to
the
snapshot-nature of the partitions.

Can anyone point me to what I need to do to get those device files
back?

(Though I agree that it could be done, I don't really consider manual
creation of the files to be a good option; I'm going to be creating
and
destroying virtual machines on this box quite often, and need the
management
tools to be working.)

On a side note: I _can_ mount these partitions, read data from them,
etc,
as
/dev/dm-1 and the like. The problem with that is that the device
files
don't necessarily refer to the same partition all the time. If you
have
dm-1..dm-6, and delete dm-2, then dm-3..dm-6 slide up one and become
dm-2..dm-5. Not handy when those device files are entered into config
files
for virtual machines.



--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx



--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • [SLE] 10.1, LVM2, and inaccessible snapshot-related logical volumes
    ... Each of these virtual machines are going to be basically identical, ... volume, and created a second as a snapshot of the first, with a couple of ... These partitions, at the time of creation, were addressable as /dev/xen/vm1 ... Can anyone point me to what I need to do to get those device files back? ...
    (SuSE)
  • Re: backup system for RHEL
    ... Are your Xen images LVs or partitions? ... Subject: backup system for RHEL ... To create the snapshot you need to have enough unpartitioned space in LVM ...
    (RedHat)
  • RE: backup system for RHEL
    ... Are your Xen images LVs or partitions? ... Subject: backup system for RHEL ... To create the snapshot you need to have enough unpartitioned space in LVM ...
    (RedHat)
  • mksnap_ffs takes 4-5 minutes?
    ... I tried making a snapshot of one of my NFS servers' ... I've done this one other machines before, ... barely used partitions, and it has always been relatively snappy. ...
    (freebsd-current)
  • Re: mksnap_ffs takes 4-5 minutes?
    ... I tried making a snapshot of one of my NFS servers' ... I've done this one other machines before, ... >>barely used partitions, and it has always been relatively snappy. ...
    (freebsd-current)
Loading