[linux-lvm] Trouble switching from LVM2 to LVM1

[linux-lvm] Trouble switching from LVM2 to LVM1

[Måns Rullgård]

I decided to take linux 2.5 with devicemapper and lvm2 for a spin.
Everything lvm related worked just fine.  Now I want to boot linux
2.4.21-preX, without devicemapper.  The problem is that vgscan runs
without errors, but all the LV device nodes are created with minor 0.
This way they all point to the same LV.  That is not what I want.  Is
there any way to get them back, or am I stuck with device-mapper?

-- 
Måns Rullgård
mru@users.sf.net

Re: [linux-lvm] Trouble switching from LVM2 to LVM1

[Alasdair G Kergon]

On Wed, Apr 16, 2003 at 07:45:16PM +0200, M?ns Rullg?rd wrote:
> without errors, but all the LV device nodes are created with minor 0.

Some time back, LVM1 introduced persistent minors, so the minor number is 
stored on disk and remembered for subsequent activations.

In LVM2, persistent minors are optional and the default is *not* to use
them, so the minor number may be different each time a device is
activated, and no minor number is stored on disk.


IIRC Exporting the VG and then importing it again will reassign LVM1 
minor numbers.

 
Alasdair
-- 
agk@uk.sistina.com

Re: [linux-lvm] Trouble switching from LVM2 to LVM1

[Måns Rullgård]

Alasdair G Kergon <agk@uk.sistina.com> writes:

> > without errors, but all the LV device nodes are created with minor 0.
> 
> Some time back, LVM1 introduced persistent minors, so the minor number is 
> stored on disk and remembered for subsequent activations.
> 
> In LVM2, persistent minors are optional and the default is *not* to use
> them, so the minor number may be different each time a device is
> activated, and no minor number is stored on disk.
> 
> 
> IIRC Exporting the VG and then importing it again will reassign LVM1 
> minor numbers.

OK, thanks.  I patched my 2.4 kernel with device-mapper instead and it
seems to be working, but it's nice to know what was going on.

-- 
Måns Rullgård
mru@users.sf.net