On 9/21/05, Carsten Otte <[EMAIL PROTECTED]> wrote: > Post, Mark K wrote: > > I strongly recommend not > > using LVM for the root file system, but when everything goes right, it > > does work. The reason it can work is that the LVM activation stuff is > > actually part of the initrd, as well as on the real root file system.
> Alternatively, LVM can setup the volume containing the rootfs automagically > when lvm is built-in the kernel. Although Suse&RedHat use the initrd to do > this, it's good to know that recovery is possible with no initrd at hand. > Thus, I'd feel save enough with rootfs on lvm. But then, when putting > /usr, /boot, /etc and such on seperate volumes it does'nt make too much > difference from the performance perspective anyway... It at least use to be true that you not only had to have the lvm kernel modules loaded you had to run vgscan and vgchange -a y to activeate the volume groups so even if you had lvm built into the kernel you still needed an initrd to run those to see your lvm file systems. Did that change in LVM2 in the 2.6 kernel? Eli ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
