[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [linux-lvm] SuSE/LVM boot problem
- From: "Andi Kleen" <ak suse de>
- To: chhellwig t-online de (Christoph Hellwig)
- Cc: ak suse de, adilger turbolabs com, linux-lvm msede com
- Subject: Re: [linux-lvm] SuSE/LVM boot problem
- Date: Wed, 31 May 2000 18:18:03 +0200
On Wed, May 31, 2000 at 06:13:08PM +0200, Christoph Hellwig wrote:
> Andi Kleen schrieb:
> > >
> > > - lilo needs to understand about lvm and use the lvm provided ways to
> > > get physical mappings.
> >
> > That's complicated. Someone did a similar hack for RAID0, but LVM is more
> > complicated than MD RAID0. Better just supply the real block numbers to lilo
> > and rerun it as needed (LVM could warn about it)
>
> Don't use lilo, use grub. I'm trying to implement lvm support in grub. The idea
> is that grub should read the first lvm on each pv. This first lv must be only on
> this pv. (and have a special name, eg lv_root, so grub can find it)
Limiting to the ``first LV'' sounds ugly. When you read the first, is it
that hard to read the second (and allow arbitary names) ?
>
> > >
> > > - the kernel needs to be able to reconstruct enough of the lvm
> > > descriptors to mount / at boot time.
>
> The kernel should know about all lvm descriptor and the /etc/lvm* should only be
> used for pvcreate an similar programs.
And who maintains that ? Using linuxrc and the normal LVM tools makes much
more sense IMHO. Just say no to kernel bloat.
-Andi
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]