From: Michael Marxmeier <mike@msede.com>
To: Andi Kleen <ak@suse.de>
Cc: Christoph Hellwig <chhellwig@t-online.de>,
adilger@turbolabs.com, linux-lvm@msede.com
Subject: Re: [linux-lvm] SuSE/LVM boot problem
Date: Wed, 31 May 2000 20:25:28 +0200 [thread overview]
Message-ID: <39355918.C2B6A94B@msede.com> (raw)
In-Reply-To: 20000531181803.A30169@gruyere.muc.suse.de
Andi Kleen wrote:
>
> 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) ?
You need to distinguish 'bootable' LV from others. This could either
be
by LV name or a 'bootable' flag. However if we need a flag anyway and
could accept the restriction to have to root fs contigous on a single
PV
and non striped we could simply save the starting block and size as
well.
This is not that different from a partition.
For example HP-UX has a simple hack in the boot area which holds
the start and size of the /stand fs such that the boot loader
and the kernel could simply handle this as a partition equivalent
during boot.
It should be possible to detect this 'bootable' flag and the
start/size
in the LVM init code without causing much kernel bloat and create the
equivalent of a partition using a fixed major/minor. vgscan could then
in user space create the device files accordingly such that the
major/minor of the LV holding the root fs is mapped accordingly.
AFAIR someone already did something similar by hacking the partition
table and creating an overlapping partition which just happened to
map to the root LV.
Michael
--
Michael Marxmeier Marxmeier Software AG
E-Mail: mike@msede.com Besenbruchstrasse 9
Phone : +49 202 2431440 42285 Wuppertal, Germany
Fax : +49 202 2431420 http://www.msede.com/
next prev parent reply other threads:[~2000-05-31 18:25 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
2000-05-31 16:18 ` Andi Kleen
2000-05-31 18:25 ` Michael Marxmeier [this message]
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=39355918.C2B6A94B@msede.com \
--to=mike@msede.com \
--cc=adilger@turbolabs.com \
--cc=ak@suse.de \
--cc=chhellwig@t-online.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).