root filesystem in lvm
[ I apologize if you receive multiple copies, but it seems that
my earlier attempts didn't make it through. Is this a closed
mailing-list ? - sm ]
A while ago, Michael Marxmeier ([email protected]) mentioned:
Quoted 4 lines
However it should be possible to use LILO. As far as i understand LILO uses partition relative block numbers to load the kernel image. We just need to make sure that they are relative to the dos style partition.
How would LILO deal with a kernel image spread over several physical partitions (or even disks) (in case you not only want a root fs on LVM but a striped/mirrored/trucmuched one) ?
Quoted 3 lines
If included statically in the kernel the lvm driver could execute the equivalent of a vgchange -ay and we should be able to mount the root file system.
That would be really neat. The initrd workaround is just that: a workaround.
Quoted 3 lines
However this will lead to some kernel bloat as some of the code which currently resides un user space in lvmlib and vgchange must also be present in the kernel.
- how hard would it be ?
- source code bloat: hopefully, the exact same source code can be shared between the kernel and the liblvm/vgchange (I deeply hate code duplication)
- kernel bloat: how bad would it be ?
how much of that extra code could be put in __INITFUNC (so that the bloat only impacts the on-disk kernel image, but not the in-memory one) ? Let's also not forget that the kernel bloat should be measured between 'linux+lvm+initrd' and 'linux+lvm+lvmroot'.
Stefan
Hello,
Quoted 3 lines
How would LILO deal with a kernel image spread over several physical partitions (or even disks) (in case you not only want a root fs on LVM but a striped/mirrored/trucmuched one) ?
Mirrored would not be such a complex thing I guess, as it simplifies to an image on one of the mirror partitions. Important is to realise that as far as lilo is concerned, only the partition where the boot image resides is important (mostly the partition where /boot resides or even the /boot partition).
Then it is up to the kernel to find the necessary code to mount the root partition and start init.
Kind regards,
winmute