Linux LVM users
 help / color / mirror / Atom feed
From: Jos Visser <josv@osp.nl>
To: Denis JARRIL <djarril@alizes.com>
Cc: linux-lvm@msede.com
Subject: Re: [linux-lvm] Configuring boot partition with LVM
Date: Mon, 07 Feb 2000 19:46:15 +0100	[thread overview]
Message-ID: <389F12F7.AE269634@osp.nl> (raw)
In-Reply-To: 000d01bf7196$61aca240$d700a8c0@alizes.com

In HP-UX, your boot lvol (/stand) must be an HFS, and it must *not* be
striped. It may be mirrored, but to boot from the mirrored lvol you must
create a complete secondary boot disks (using pvcreate -B and then after
having created the mirrors running lvlnboot).

In my opinion, mirroring should be made a part of the LVM because then
the LVM will be in complete control of the mirrors, which allows other
nice things such as lvsplit/lvmerge and others.

++Jos

Denis JARRIL wrote:
> 
> I don't agree.
> With HP-UX, you can boot from anywhere. You just have to create a contiguous
> and HFS LV to boot on. I don't know where the problem comes from on Linux
> but I tried to make a root miror and it didn't work. The test of the md
> volumes was good but the system stopped just after, when it passes from the
> ramdisk to the disk. Bad thing. If this problem is resolved, LVM on Linux
> will be able to work.
> 
> ----- Message d'origine -----
> De : Jos Visser <josv@osp.nl>
> � : <Fabian.Herschel@suse.de>
> Cc : <linux-lvm@msede.com>
> Envoy� : lundi 7 f�vrier 2000 17:37
> Objet : Re: [linux-lvm] Configuring boot partition with LVM
> 
> >  Lilo
> > should also learn how to boot a kernel fom a striped volume...
> 
> Hi,
> 
> I don't think you fully appreciate the request you're making here.
> Commercial Unices such as HP-UX and Solaris can not boot from striped
> volumes for about the same reasons why it would be difficult to have
> LILO read from a striped volume: the implications are just too
> horrendous to comtemplate.
> 
> Typically I don't care that my boot partition/lv can not be striped. The
> I/O rates into that volume are just not high enough to need striping.
> Why not put our efforts to something else which is more important right
> now.?
> 
> ++Jos
> 
> --
> All the rivers run into the sea; yet the sea is not full; unto
> the place from whence the rivers come, thither they return again.

-- 
All the rivers run into the sea; yet the sea is not full; unto
the place from whence the rivers come, thither they return again.

  parent reply	other threads:[~2000-02-07 18:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-04 17:29 [linux-lvm] Configuring boot partition with LVM Jim Cain
2000-02-07  9:37 ` Fabian.Herschel
2000-02-07 13:11   ` Luca Berra
2000-02-07 16:37   ` Jos Visser
2000-02-07 16:45     ` Fabian.Herschel
     [not found]     ` <000d01bf7196$61aca240$d700a8c0@alizes.com>
2000-02-07 18:46       ` Jos Visser [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-02-10  7:14 Andreas Dilger
2000-02-14 16:23 ` Luca Berra

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=389F12F7.AE269634@osp.nl \
    --to=josv@osp.nl \
    --cc=djarril@alizes.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