[linux-lvm] vgimport/vgexport commands when logically moving disks between systems

Patrick Caulfield pcaulfie at redhat.com
Thu Dec 14 13:49:29 UTC 2006

Dave wrote:
> Hi Patrick,
> Thanks for clarifying the status of LVM1 (ie. *not* a clustering tool).  That's
> somewhat surprising since it does include an LVM script in the resource.d directory.
>  In any case, we're not in a huge rush to upgrade to LVM2 unless it really is
> necessary, as these are RH AS3 boxes running the 2.4.21-47.ELsmp kernel, and the
> docs I've read suggest LVM2 really needs/wants to run under a 2.6.x kernel.

Yes. there are device-mapper patches for 2.4 but it's really recommended to run 2.6.

> If direct-io to metadata could be set as an option under LVM1, assuming that isn't
> the default, that would be helpful.  But, it sounds like no one really wants to
> support LVM1 anymore?!

That's true. lvm1 is in maintenance mode for RHEL3.

> Assuming we want to go forward with an upgrade to LVM2 on the current systems, how
> involved is that procedure?  Do we risk losing all our data?

No. lvm2 can read and write lvm1 metadata. you can upgrade it to lvm2 format metadata with a single command (vgconvert)


More information about the linux-lvm mailing list