booting w/o initrd
Quoted 5 lines · Ulf
Imagine a LV lying in some VG of your PV.
This LV has to be allocated in a continuous range of PEs, especially it must not cross the border between two disks. With these requirements fullfilled, the LV could be described completely by the number of the its beginning sector on the disk and its length in sectors.
This is what IBM also needs for its "boot LV". It is required that the BLV is contiguous on one disk. Normally, it only needs to be 1 PP in size, but it can sometimes grow to 2 PPs in size. I think Linux should have enough space in 4/8 MB for a boot partition considering Tom's root/boot disk has a whole system on 1.8MB floppy...
Quoted 4 lines
But what if ... you want to resize the root?
Even when booting via initrd, you cannot resize the root while it is mounted.
Actually, it IS possible to resize mounted ext2 filesystems with my online resize tools (LVM is required, of course). Have a look at:
http://www-mddsp.enel.ucalgary.ca/People/adilger/online-ext2/
for more information.
Good luck on your project. I think this is a much better solution than using initrd, since it is more like a normal system.
Cheers, Andreas
Signature · 3 lines
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- DogbertHi!
Quoted 5 lines · Andreas Dilger
This is what IBM also needs for its "boot LV". It is required that the BLV is contiguous on one disk. Normally, it only needs to be 1 PP in size, but it can sometimes grow to 2 PPs in size. I think Linux should have enough space in 4/8 MB for a boot partition considering Tom's root/boot disk has a whole system on 1.8MB floppy...
Right! A 4M partition for /boot should be enough to hold enough kernels even for those who love experimenting with serveral versions...
...and if not, just give /boot 8M...
Quoted 9 lines
Quoted 4 lines
But what if ... you want to resize the root?
Even when booting via initrd, you cannot resize the root while it is mounted.
Actually, it IS possible to resize mounted ext2 filesystems with my online resize tools (LVM is required, of course). Have a look at:
http://www-mddsp.enel.ucalgary.ca/People/adilger/online-ext2/
for more information.
Ok - I knew that page but I donnow how stable this is, so I didn't include it in my argumentation.
Quoted 2 lines
Good luck on your project. I think this is a much better solution than using initrd, since it is more like a normal system.
It is tested for some weeks on two systems @myhome and Peter has two systems up this way since last weekend (Peter: correct me if I'm wrong with that date...).
I think the idea has proven to be handable and reliable now I'd like to find an easy way to install such a system.
And even if it is not needed today, somewhen LVM might be changed in a way that stopping it cleanly on shutdown will become a must. So I feel better having an init.d script starting and stopping LVM and I have no idea on doing this with an initrd based system...
...and if all else fails, I can access /boot and / with standard rescue disks...
Bye for now!
Ulf.
Quoted 1 line · Ulf Bartelt
[]
Quoted 2 lines
And even if it is not needed today, somewhen LVM might be changed in a way that stopping it cleanly on shutdown will become a must.
[]
What is about power failure for example? Or kernel panic? Or hardware error? Does it mean that there will be no ability to bring lvm up again in such a cases!? But clean filesystem umount is a must, but there is a fsck here that is started (automatically) if that "must" didn't satisfied....
Quoted 8 lines · Michael Ju. Tokarev
[]
Quoted 2 lines
And even if it is not needed today, somewhen LVM might be changed in a way that stopping it cleanly on shutdown will become a must.
[]
What is about power failure for example? Or kernel panic? Or hardware error? Does it mean that there will be no ability to bring lvm up again in such a cases!? But clean filesystem umount is a must, but there is a fsck here that is started (automatically) if that "must" didn't satisfied....
For now, cleanly deactivating LVM before shutdown is not neccessary. Otherwise bringing up LVM from an initial ram disk and switching the root would bring the systems in trouble as there are no actions like switching back to a ram disk on shutdown, unmount the "real" root, stop LVM and stop the system...
Filesystems must be unmounted before shutdown. But if something crashes, a fsck inspects the filesystem on the next system startup. I expect LVM to behave similar if bringing LVM down before shutdown will be required.