From: "Andi Kleen" <ak@suse.de>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Andi Kleen <ak@suse.de>,
Linux LVM mailing list <linux-lvm@msede.com>,
idsfa@visi.com
Subject: Re: [linux-lvm] LVM support for LILO
Date: Fri, 8 Sep 2000 00:46:40 +0200 [thread overview]
Message-ID: <20000908004640.A24191@gruyere.muc.suse.de> (raw)
In-Reply-To: <200009072239.QAA09511@lynx.turbolabs.com>; from adilger@turbolinux.com on Thu, Sep 07, 2000 at 04:39:39PM -0600
On Thu, Sep 07, 2000 at 04:39:39PM -0600, Andreas Dilger wrote:
> Andi Kleen, you write:
> > I did some similar work. I implemented an LVM_BMAP ioctl for LVM that
> > simply translates a given block to a (dev_t, blocknr in dev). lilo
> > simply does a normal FIOBMAP and then calls LVM_BMAP for every block
> > it gets. When the dev_t ever changes it complains loudly. Then it does
> > its normal work with the resulting blocks.
>
> Do you have the corresponding patches to LILO? Have you ever tried
> submitting them to the LILO maintainers?
I hacked lilo, but I never tested them really because I didn't have a spare
HD to experiment with the changed PV format at that time (I noticed the
problem with the PV format only after I did that work :-() You can have
the untested patches if you want. From visual inspection the translated
blocks looked ok.
A full solution requires more work, e.g. at least a LV flag so that
LVM can urge the user to rerun lilo after a *move. Support in lilo for LVs
spread over multiple devices would also be nice (I just cheated by requiring
it all on a single device)
>
> > It works ok. The only problem is that a standard PV cannot be used for
> > booting, because it does leave any space for a MBR (it probably needs
> > a PV format revision that simply leaves 4K free)
>
> I think if you make a partition on your boot disk (even if it is the
> full size of the disk), then you will have enough space for a MBR. No
> need to change LVM formats. You can use full-disk PVs if you want for
> your other disks, but it quiets the boot process down a bit if you have
> a partition on the disk (or at least it complained the last time I tried
> a full-disk PV).
It just does not make much sense then, because with a DOS partition table
you can as well have a partition based /boot
-Andi
next prev parent reply other threads:[~2000-09-07 22:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-07 18:25 [linux-lvm] LVM support for LILO Andreas Dilger
2000-09-07 21:43 ` Andi Kleen
2000-09-07 22:39 ` Andreas Dilger
2000-09-07 22:46 ` Andi Kleen [this message]
2000-09-07 23:44 ` Andreas Dilger
2000-09-08 14:25 ` Andi Kleen
2000-09-08 0:11 ` Heinz J. Mauelshagen
2000-09-07 22:14 ` Andi Kleen
2000-09-07 23:00 ` Andi Kleen
2000-09-08 0:02 ` Heinz J. Mauelshagen
2000-09-07 23:29 ` Andreas Dilger
2000-09-08 13:02 ` Heinz J. Mauelshagen
2000-09-08 13:47 ` Luca Berra
2000-09-08 19:09 ` Heinz J. Mauelshagen
2000-09-08 14:03 ` Michael J Kellen
2001-02-27 0:30 ` Ralph Jennings
-- strict thread matches above, loose matches on Subject: below --
2000-09-08 19:39 Andreas Dilger
2000-09-08 19:50 Andreas Dilger
2000-09-09 7:44 ` Luca Berra
2000-09-09 10:07 ` Christoph Hellwig
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=20000908004640.A24191@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=adilger@turbolinux.com \
--cc=idsfa@visi.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).