All of lore.kernel.org
 help / color / mirror / Atom feed
From: lembark@wrkhors.com
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Root on LV
Date: Wed, 19 Sep 2001 14:43:04 -0500	[thread overview]
Message-ID: <4740000.1000928584@duke.wrkhors.com> (raw)
In-Reply-To: <OFB98B66D9.BF1F5CB9-ON85256ACC.0066E63E@raleigh.ibm.com>


-- Steve Pratt <slpratt@us.ibm.com> on 09/19/01 13:54:23 -0500

>> .Q:  Why bother to put 64MB on an LVM?
> 
>> The root volume doesn't grow much (make it 128MB and it'll never need to
>> grow).
> 
> Sure, you could always do this.
> 
>> If you ever have a problem with LVM you'll end up with an unbootable
>> system...
> 
> Right, which is why volume managers need to be really stable and robust.
> Bottom line is that if this is the confidence level you have in your
> volume manager (whether it is LVM or EVMS), I would question putting any
> data on it.

That's like saying you don't need ABS brakes because tire makers
should make ones with really, really good traction.  If you look
at the commercial LVM systems (e.g., HP's) they get around LVM
failures by having a non-trivial boot system that allows side-
stepping LVM at boot time via the command line.  This is done on
HP by requring /dev/vg00/lvol[123] to be contiguous and starting
at offset 0 on the VG.  You can boot vmunix -lm if LVM gets toasted
and at least get the boot, swap and root volumes on line to fix
the problem.  Lacking that much intelligence in the hardware level 
of Intel boot rom's you are one helluvalot sa[fn]er to put the
root and primary swap on /dev/[hs]da[12] and go from there.  

sl

  reply	other threads:[~2001-09-19 19:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19 18:54 [linux-lvm] Root on LV Steve Pratt
2001-09-19 19:43 ` lembark [this message]
2001-09-20  5:15 ` Adrian Phillips
  -- strict thread matches above, loose matches on Subject: below --
2001-09-17 14:26 Steve Pratt
2001-09-18 17:23 ` lembark
2001-09-06 14:03 dobos_s
2001-09-06 14:10 ` josv
2001-09-10 11:31   ` Heinz J . Mauelshagen
2001-09-06 14:42 ` svetljo
2001-09-06 15:37   ` Andreas Dilger
2001-09-06 16:35     ` svetljo
2001-09-06 17:52       ` Luca Berra
2001-09-10 11:29     ` Heinz J . Mauelshagen
2001-09-06 16:53 ` lembark

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=4740000.1000928584@duke.wrkhors.com \
    --to=lembark@wrkhors.com \
    --cc=linux-lvm@sistina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.