[linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[Mark Phillips]

Hi,

I am currently running a 2.4.0-test9 kernel with LVM compiled in and
with associated software, version 0.8.final.  Everything works fine
here.

I tried compiling the final version of 2.4.0 with LVM compiled in, but
when I tried booting, it complained that it didn't know about my LVM
devices!  It seems strange that 2.4.0-test9 works fine but 2.4.0
doesn't.  Could it be that I need to upgrade to 0.9 of the LVM
software?

What else could be the problem?

Thanks,

Mark.

-- 
_/~~~~~~~~\___/~~~~~~\____________________________________________________
____/~~\_____/~~\__/~~\__________________________Mark_Phillips____________
____/~~\_____/~~\________________________________mark@ist.flinders.edu.au_
____/~~\HE___/~~\__/~~\APTAIN_____________________________________________
____/~~\______/~~~~~~\____________________________________________________
__________________________________________________________________________
        "They told me I was gullible ... and I believed them!" 

Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[Benoit SERRA]

Mark Phillips wrote:
> 
> Hi,
> 
> I am currently running a 2.4.0-test9 kernel with LVM compiled in and
> with associated software, version 0.8.final.  Everything works fine
> here.
> 
> I tried compiling the final version of 2.4.0 with LVM compiled in, but
> when I tried booting, it complained that it didn't know about my LVM
> devices!  It seems strange that 2.4.0-test9 works fine but 2.4.0
> doesn't.  Could it be that I need to upgrade to 0.9 of the LVM
> software?
> 

With 2.4.0, the LVM version is 0.9, which is not compatible with 0.8.
So you have to upgrade your user space tools to 0.9, and to migrate your
0.8final LVM volumes to 0.9
volumes. For me, the safiest way to do this is to make a backup of your
data, crash all your LVm setup, reboot on 2.4.0, create your VG and LV
with  0.9 user space tools, and then restore data.
I think there is some way to migrate without restoring data, check the
list archive for this.

Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[Mark Phillips]

dmeyer@dmeyer.net [dmeyer@dmeyer.net] wrote:
> In article <20010124184810.R715@ist.flinders.edu.au> you write:
> > I tried compiling the final version of 2.4.0 with LVM compiled in, but
> > when I tried booting, it complained that it didn't know about my LVM
> > devices!  It seems strange that 2.4.0-test9 works fine but 2.4.0
> > doesn't.  Could it be that I need to upgrade to 0.9 of the LVM
> > software?
> 
> You got it - you need the 0.9 user tools from ftp.sistina.com.  BTW,
> you might want to think about going to 0.9.1beta2 - it's got some
> important fixes and it at least as stable as 0.9.

If I upgrade from 0.8 to 0.9.1beta2, will it be backward compatible?
That is, will I still be able to use LVM fine under my current
2.4.0-test9 kernel?

Thanks,

Mark.

-- 
_/~~~~~~~~\___/~~~~~~\____________________________________________________
____/~~\_____/~~\__/~~\__________________________Mark_Phillips____________
____/~~\_____/~~\________________________________mark@ist.flinders.edu.au_
____/~~\HE___/~~\__/~~\APTAIN_____________________________________________
____/~~\______/~~~~~~\____________________________________________________
__________________________________________________________________________
        "They told me I was gullible ... and I believed them!" 

Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[dirk.derycke]

Hi all,

for me the upgrade from 2.4.0-test12 to 2.4.0 was simple. I upgraded the
user tools to 0.9
rebooted with 2.4.0. Important note: my root partition is NOT LVM.
Then I executed the vgscan from the 0.9 tools which detected the 0.8 LVM
data, then I activated the volume group and mounted the LV's.

A backup however is always a safe thing to do. But normally the above
procedure should work fine...
Note that I had a 2.2.14 with 0.7 tools first before 2.4.0-testXX and
didn't have to backup and restore data...

What would be the point of having industrial strength disk management when
you have to backup and restore
every software upgrade (imagine hundreds of gigs)?.

regards,

Dirk





Benoit SERRA <bs@infologic.fr>@sistina.com on 01/24/2001 09:31:22 AM

Please respond to linux-lvm@sistina.com

Sent by:  linux-lvm-admin@sistina.com


To:   linux-lvm@sistina.com
cc:

Subject:  Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM


Mark Phillips wrote:
>
> Hi,
>
> I am currently running a 2.4.0-test9 kernel with LVM compiled in and
> with associated software, version 0.8.final.  Everything works fine
> here.
>
> I tried compiling the final version of 2.4.0 with LVM compiled in, but
> when I tried booting, it complained that it didn't know about my LVM
> devices!  It seems strange that 2.4.0-test9 works fine but 2.4.0
> doesn't.  Could it be that I need to upgrade to 0.9 of the LVM
> software?
>

With 2.4.0, the LVM version is 0.9, which is not compatible with 0.8.
So you have to upgrade your user space tools to 0.9, and to migrate your
0.8final LVM volumes to 0.9
volumes. For me, the safiest way to do this is to make a backup of your
data, crash all your LVm setup, reboot on 2.4.0, create your VG and LV
with  0.9 user space tools, and then restore data.
I think there is some way to migrate without restoring data, check the
list archive for this.

_______________________________________________
linux-lvm mailing list
linux-lvm@sistina.com
http://lists.sistina.com/mailman/listinfo/linux-lvm

Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[Jan Niehusmann]

On Wed, Jan 24, 2001 at 09:31:22AM +0100, Benoit SERRA wrote:
> I think there is some way to migrate without restoring data, check the
> list archive for this.

Of course there is, 0.9 understands 0.8's on-disk structure, only the interface
between kernel and userspace has changed.

But it's always a good idea to make a backup ;-)

Jan

Re: [linux-lvm] Fwd: 2.4.0 kernel doesn't see LVM

[Benoit SERRA]

dirk.derycke@icos.be wrote:
> 
> Hi all,
> 
> for me the upgrade from 2.4.0-test12 to 2.4.0 was simple. I upgraded the
> user tools to 0.9
> rebooted with 2.4.0. Important note: my root partition is NOT LVM.
> Then I executed the vgscan from the 0.9 tools which detected the 0.8 LVM
> data, then I activated the volume group and mounted the LV's.
> 
> A backup however is always a safe thing to do. But normally the above
> procedure should work fine...
> Note that I had a 2.2.14 with 0.7 tools first before 2.4.0-testXX and
> didn't have to backup and restore data...
> 
> What would be the point of having industrial strength disk management when
> you have to backup and restore
> every software upgrade (imagine hundreds of gigs)?.
> 
> regards,
> 
> Dirk
> 

I'm not sure that playing with version of critical software layers such
as LVM is a good idea if you value your data.

My experience say that you should make a backup of your data before
trying to upgrade to 0.9, but I'm parano�d.