[Gllug] One step forward - 2 steps back

John Winters john at sinodun.org.uk
Tue Jul 20 14:07:06 UTC 2004

On Tue, 2004-07-20 at 14:15, Tethys wrote:
> John Winters writes:
> >This box has a couple of (not terribly important) LVM partitions but
> >it seems AFAICS that lvm 1.0 is not compatible with kernel 2.6. Am I
> >right in that understanding?
> No, you're not. I have a mix of LVM1 and LVM2 on my machine, running
> quite happily with a 2.6 kernel:
>     leto:~# uname -r
>     2.6.7
>     leto:~# pvscan
>       PV /dev/hdd5   VG os    lvm1 [4.33 GB / 0    free]
>       PV /dev/hda6   VG fc2   lvm2 [100.95 GB / 68.95 GB free]
>       Total: 2 [105.27 GB] / in use: 2 [105.27 GB] / in no VG: 0 [0   ]
> What aren't compatible with 2.6 are the LVM1 userland tools. If you're
> using a 2.6 kernel, you'll need the LVM2 tools. The on disk format is
> identical between LVM1 and LVM2, so there is no upgrade path per se.

OK.  Removed the lvm1 tools and installed the lvm2 ones.  However, I
still don't seem to be able to access the logical volumes:

bennet:~# pvscan
  PV /dev/hdb4   VG data   lvm1 [228.70 GB / 123.82 GB free]
  Total: 1 [228.70 GB] / in use: 1 [228.70 GB] / in no VG: 0 [0   ]
bennet:~# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "data" using metadata type lvm1
bennet:~# lvscan
  inactive          '/dev/data/vmware' [4.88 GB] normal
  inactive          '/dev/data/cdwork' [100.00 GB] normal
bennet:~# mount -a
mount: /dev/data/cdwork is not a valid block device
mount: /dev/data/vmware is not a valid block device

The dm_mod module is loaded.  Is there something else I need to make
them accessible?


Gllug mailing list  -  Gllug at gllug.org.uk

More information about the GLLUG mailing list