On Feb 26, 2002 13:27 +0100, Thorsten Sauter wrote: > again a little question. i have currently the following configuration: > > # fdisk -l /dev/hda > /dev/hda1 1 1115 8e Linux LVM > > /dev/hda1 => rootvg > > rootvg > /dev/rootvg/root / > /dev/rootvg/usr /usr > /dev/rootvg/boot /boot > > Why this configuration is so bad? Is it better to leave the /boot on an > "normal" ext2 filesystem? But, what files need the kernel from /boot to > bootup the system correctly? I think the kernel will be stored in the > master boot record with lilo? Actually, if you use LILO it doesn't need to understand anything about LVM in order to boot. LILO 22.1 (or a patched LILO 21.6+) will talk with the LVM driver to map out the blocks for the kernel and initrd into the MBR, so that when you are booting it just reads the blocks by number. Some possible problems include the fact that /boot may be too far from the start of the disk and older BIOSes have problems with kernel/initrd over cylinder 1024. Also, you need to run LILO _every_ time you update your kernel and initrd, because it has to re-map all of the blocks into the MBR. The real danger is having your / partition in LVM, because if there is ever a problem with your LVM configuration then you cannot access the right tools, and also your LVM config backups are inaccessible. Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/ _______________________________________________ linux-lvm mailing list linux-lvm@sistina.com http://lists.sistina.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
