Linux LVM users
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <724b581f59b221086926026402b50126@interlinx.bc.ca>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Chicken and egg problem..
Date: Wed Nov 21 12:36:02 2001	[thread overview]
Message-ID: <20011121144408.GI9907@pc.ilinx> (raw)
In-Reply-To: <7510000.1006331425@dizzy>

On Wed, Nov 21, 2001 at 02:30:25AM -0600, Steven Lembark wrote:
> 
> The kernel panic is extactly why you probably wouldn't
> want to use only LVM on the system.

I do it.  Only my boot partition is a regular ol' partition.  I won't
say I haven't had problems that I had to recover from in the past with
an LVM root, but luckily enough my distro vendor's LVM support is
decent and their BOOT kernel/media has an LVM module built for it.

> Leaving the root
> volume (a.k.a., '/'), primary swap and probably /var on
> the first three partitions of the boot device will make
> your life enormously simpler in the long run.

I completely disagree.  Eventually you will get to a point where an
upgrade of your system will require more space in / or /usr and even
just normal usage will want more space in /var.  Being able to expand
these easily with LVM is awesome!

> This is pretty much the only way you'll be able to
> convienently recover from any LVM problems in the future.

Just use a good boot disk.  You are even luckier if your distro
vendor's stock kernel and/or media support LVM.

> Otherwise you'll need bootable media floating around.

Of course.  Don't you always?  :-)

b.

-- 
Brian J. Murrell

  parent reply	other threads:[~2001-11-21 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21  6:51 [linux-lvm] Chicken and egg problem Georges Giralt
2001-11-21  8:31 ` Steven Lembark
2001-11-21  8:48   ` Georges Giralt
2001-11-21 12:36   ` Brian J. Murrell [this message]
2001-11-21 20:32     ` Steven Lembark
2001-11-21 12:36 ` Brian J. Murrell

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=20011121144408.GI9907@pc.ilinx \
    --to=724b581f59b221086926026402b50126@interlinx.bc.ca \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox