linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Urs Thuermann <urs@isnogud.escape.de>
Cc: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LILO+LVM:  Fatal: This version of LVM does not support boot LVs
Date: Fri Feb 15 16:12:02 2002	[thread overview]
Message-ID: <20020215151015.H14054@lynx.adilger.int> (raw)
In-Reply-To: <m2heoivkr6.fsf@isnogud.escape.de>; from urs@isnogud.escape.de on Fri, Feb 15, 2002 at 04:15:57PM +0100

On Feb 15, 2002  16:15 +0100, Urs Thuermann wrote:
> I installed lilo-22.2 and moved my /boot from /dev/sda1 to my root FS
> which is on LVM /dev/vg0/root.  When running lilo I get the message
> 
>     Fatal: This version of LVM does not support boot LVs

I suppose that in your case this message is misleading.  It should also
say that it doesn't support booting from striped volumes.

> which is from Andreas' LILO patch.  lilo checks wether the logical
> blocks 0 and 255 are also 255 apart from each other on the physical
> device (assuming the device is the same).
> 
> This clearly works only on non-striped and contigous LVs (which is why
> it doesn't work for me since /dev/vg0/root is striped).
> I suppose this is intended, but why?

Well, it was always my understanding that this is a BIOS limitation.
I implemented this test because LILO also refuses to boot from RAID-0
(striped) devices.

> the lilo loader load blocks from different devices and blocks which
> are not in ascending order?  The 5-byte structure describing the
> blocks to load contains the device: (from lilo/README):
> 
>      sector    [1..63] plus 2 high bits of Cylinder
>      cylinder  [0..1023] low eight bits in this byte
>      device    [0..3] for floppies, [0x80..0x8F] for hard disks
>      head      [0..254] no, the max is 254, not 255
>      count     [1...] number of sectors to transfer
> 
> So, why not support booting from striped and non-contiguos LVs?

Well, if this is the case, and it's not a BIOS limitation, feel free
to fix the LILO code and test it.  If it works, then send a patch to
the LILO maintainer.

I for one think it is a terrible idea to boot from a striped device.
This doubles the chance that a disk failure will make your system
unbootable, in addition to all the possible problems you can have
with your LVM config.

What is your motivation for doing this in the first place?  Let me
guess "increased performance"...

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/

      reply	other threads:[~2002-02-15 16:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15  9:20 [linux-lvm] LILO+LVM: Fatal: This version of LVM does not support boot LVs Urs Thuermann
2002-02-15 16:12 ` Andreas Dilger [this message]

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=20020215151015.H14054@lynx.adilger.int \
    --to=adilger@turbolabs.com \
    --cc=linux-lvm@sistina.com \
    --cc=urs@isnogud.escape.de \
    /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).