From: Christoph Hellwig <chhellwig@t-online.de>
To: ak@suse.de
Cc: adilger@turbolabs.com, linux-lvm@msede.com
Subject: Re: [linux-lvm] SuSE/LVM boot problem
Date: Wed, 31 May 2000 18:13:08 +0200 [thread overview]
Message-ID: <12xB7E-0izhAGC@fwd05.sul.t-online.de> (raw)
In-Reply-To: 20000531110128.A22796@gruyere.muc.suse.de
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)
> >
> > - 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.
Christoph
next prev parent reply other threads:[~2000-05-31 16:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-03 7:38 [linux-lvm] SuSE/LVM boot problem Michael Marxmeier
2000-05-03 16:53 ` dgould
2000-05-31 9:01 ` Andi Kleen
2000-05-31 16:13 ` Christoph Hellwig [this message]
2000-05-31 16:18 ` Andi Kleen
2000-05-31 18:25 ` Michael Marxmeier
2000-06-01 12:15 ` Ulf Bartelt
2000-06-01 9:01 ` David Gould
-- strict thread matches above, loose matches on Subject: below --
2000-05-04 12:18 Shaw, Marco
2000-05-03 23:50 Andreas Dilger
2000-05-04 2:28 ` dgould
2000-05-04 5:21 ` Michael Loftis
2000-05-04 2:38 ` Eric M. Hopper
2000-05-03 18:09 Andreas Dilger
2000-05-03 21:01 ` Eric M. Hopper
2000-05-02 5:20 Marco Shaw
2020-11-27 16:17 ` Michael Marxmeier
2000-05-02 18:41 ` dgould
2000-05-02 21:22 ` Jan Niehusmann
2000-05-02 22:18 ` Heinz Mauelshagen
2000-05-03 10:05 ` Ulf Bartelt
2000-05-31 8:40 ` Andi Kleen
2000-05-03 0:15 ` Marco Shaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12xB7E-0izhAGC@fwd05.sul.t-online.de \
--to=chhellwig@t-online.de \
--cc=adilger@turbolabs.com \
--cc=ak@suse.de \
--cc=linux-lvm@msede.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).