John McNulty <johnmcn1@xxxxxxxxxxxxxx> writes:
> On Tue, Jun 30, 2009 at 5:26 AM, Goswin von Brederlow<goswin-v-b@xxxxxx> wrote:
>>
>> Hmm, do I understand this right that you want 2 partitions. One for
>> /boot and one for everything else on lvm?
>>
>> Just a crazy idea. But why not put /boot on lvm too and use grub2 or
>> lilo as bootloader? Or does Kickstart not allow that?
>
> I didn't think that booting from an LVM device was supported, whether
> it's sitting on an md raid device or not. How is the bootloader meant
> to find the kernel and initrd without first constructing the VG and
> mounting the /boot Logical Volume. It's been quite a while since I
> looked (we get into the habit of doing things the same way) but last
> time I checked this didn't work.
>
> Rgds,
>
> John
In case of grub2: It does support both raid and lvm. The raid
superblocks are parsed to construct mdX devices and the lvm metadata
is parsed to locate lvm logical volumes. So you could say it does
construct the LV and mounts the FS.
In case of lilo: Lilo only stores a list of blocks where the
kernel/initrd are on the device. Afaik each component device of a raid
stores the the block numbers for the kernel/initrd on that component
device. So no matter which component device boots it will find the
kernel/initrd on the same device. The raid1 and lvm are completly
circumvented.
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
