From: David Gould <dg@suse.com>
To: Andi Kleen <ak@suse.de>
Cc: dgould@suse.com, adilger@turbolabs.com, linux-lvm@msede.com
Subject: Re: [linux-lvm] SuSE/LVM boot problem
Date: Thu, 1 Jun 2000 02:01:31 -0700 [thread overview]
Message-ID: <20000601020131.E17555@archimedes.suse.com> (raw)
In-Reply-To: <20000531110128.A22796@gruyere.muc.suse.de>; from ak@suse.de on Wed, May 31, 2000 at 11:01:28AM +0200
On Wed, May 31, 2000 at 11:01:28AM +0200, Andi Kleen wrote:
> On Wed, May 03, 2000 at 09:53:26AM -0700, dgould@suse.com wrote:
> > If I have understood this, we need the following to make this
> > work (some of this may already exist):
> >
> > - lvm needs to provide an way for other programs to translate logical
> > blocks to physical
>
> A physical equivalent to FIBMAP. Not too hard to implement I think.
Yes. That is what I meant.
> > - lvm needs to have a way of tracking/enforcing/satisfying the constraint
> > that specified lvs need to be in the bios bootable physical area
>
> That's pretty much impossible. How would e.g. LVM find out that the scsi
> controller of disk X does not have a boot rom? You have to trust the user there.
Fine. Trusting the user is ok, but I like the marked bootable idea to
protect against arbitrary reconfigs.
> > - 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)
I meant only that lilo needs to call the lvm flavored FIBMAP, to get the
block numbers. That is, lilo will need a small patch.
> > - the kernel needs to be able to reconstruct enough of the lvm
> > descriptors to mount / at boot time.
>
> That's handled in the initrd (lilo loads kernel + initrd, initrd contains
> LVM tools)
Ok.
-dg
--
David Gould dg@suse.com
SuSE, Inc., 580 2cd St. #210, Oakland, CA 94607 510.628.3380
C++ : an octopus made by nailing extra legs onto a dog
next prev parent reply other threads:[~2000-06-01 9:01 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
2000-06-01 12:15 ` Ulf Bartelt
2000-06-01 9:01 ` David Gould [this message]
-- 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=20000601020131.E17555@archimedes.suse.com \
--to=dg@suse.com \
--cc=adilger@turbolabs.com \
--cc=ak@suse.de \
--cc=dgould@suse.com \
--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).