root filesystem in lvm
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
Quoted 3 lines · Stefan Monnier
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) ?
Hard, real hard, lilo uses only bios calls, and in 512bytes you just cannot fit anithing better, all other os that use lvm have a /stand partition at the beginning of the disk, it can be mirrored but it must necessarily be contiguous
Quoted 5 lines
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.
i personally love modular kernels, so i'd use initrd anyway, but i agree vgchange -a y could be handled by the kernel.
but i also believe that this would be easier to debug/mantain in user space.
L.
Signature · 2 lines
Luca Berra -- [email protected] Communications Media & Services S.r.l.