Migrating LVM1->LVM2 and kernel 2.4->2.5
I wonder whether there's any advantage for migrating to LVM2 on 2.4 kernels, if everything works OK?
But, as I see in kernel 2.5, there's no LVM by name, just a low-level device mapper. Does it mean that in order to even try out kernel 2.5 on an LVM1 system, I have to migrate to LVM2 first? Is there any way to "migrate" while being able to roll back to LVM1? Does it depend on whether the root partition is LVM? One of mine is, LVM1 too.
Signature · 2 lines
Cheers, Alexy Khrabrov :: www.setup.org :: Age Quod Agis
Quoted 3 lines · Alexy Khrabrov
I wonder whether there's any advantage for migrating to LVM2 on 2.4 kernels, if everything works OK?
You could use the new atomic metadata format, configure the system more flexibly with the new config file and use the human readable metadata backups in the event of problems, just to name a few advantages. Personally I think it's worth upgrading for the 'lvs', 'pvs' and 'vgs' commands alone, I always found the *display commands overly verbose.
Quoted 5 lines
But, as I see in kernel 2.5, there's no LVM by name, just a low-level device mapper. Does it mean that in order to even try out kernel 2.5 on an LVM1 system, I have to migrate to LVM2 first? Is there any way to "migrate" while being able to roll back to LVM1?
LVM2 supports the LVM1 metadata, so there is no migration as such. If you have a kernel with dm built in and the LVM2 tools you can use LVM2. If you want to roll back to LVM1 just switch back to an LVM1 kernel and tools.
If you want to run an 2.5 kernel you will have to use LVM2.
Quoted 2 lines
Does it depend on whether the root partition is LVM? One of mine is, LVM1 too.
We have never run a root from an LVM2 lv, but there's no reason why it wont work. But of course don't expect the initrd built with lvmcreate_initrd to work.
- Joe