LVM migration for 2.4->2.6, fallback path?
Hi,
I understand that the following three combinations work (assuming 2.4.24/2.6.1):
Userspace Kernelspace
------------------------------------------
LVM1 2.4 LVM LVM2 2.4 + devmapper patch LVM2 2.6
But will LVM2 + 2.4 LVM work? LVM1 + 2.6 will not.
I presume neither works, but if there is a way, I'd like to know to save myself some work.
Oh, and while I'm at it, what good is the "old ioctl" switch in kernel space? I am currently trying without and it works fine with a current LVM2 version (which is presumably how things are meant to be).
TIA,
Signature · 3 lines
Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95
Quoted 5 lines · Matthias Andree
Hi,
I understand that the following three combinations work (assuming 2.4.24/2.6.1):
Quoted 7 lines
Userspace Kernelspace
------------------------------------------LVM1 2.4 LVM LVM2 2.4 + devmapper patch LVM2 2.6But will LVM2 + 2.4 LVM work? LVM1 + 2.6 will not.
Just don't resize your volumes in 2.6, and you'll be fine. Resizing causes 'vendor lock in' though ;-)
Quoted 6 lines
I presume neither works, but if there is a way, I'd like to know to save myself some work.
Oh, and while I'm at it, what good is the "old ioctl" switch in kernel space? I am currently trying without and it works fine with a current LVM2 version (which is presumably how things are meant to be).
Just use the new ioctl, the old is just for compatibility with an old lvm2 userspace. Clearly you don't have that.
Signature · 1 line
Erik Hensema <[email protected]>