All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Chicken and egg problem..
Date: Wed Nov 21 20:32:02 2001	[thread overview]
Message-ID: <46460000.1006374706@dizzy> (raw)
In-Reply-To: <20011121144408.GI9907@pc.ilinx>


-- "Brian J. Murrell" <724b581f59b221086926026402b50126@interlinx.bc.ca>

> 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.

Luck has a rather nasty way of running out just when
you need the system. I've spent way too much time
helping extricate people from LVM problems to run
my root file system on it. The "all LVM" systems
from HP and Sun depend on a non-braindead boot ROM
and the ability to fake out the file system with
sequentail LV's that look to the boot loader like
partitions. On HP's this lets you boot -lm, fix
things and reboot. Lacking this option on Intel
systems, I'd make a point of leaving the main boot
area on a native hardware format.

>
>> 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!

Who said anything about not having /usr on LVM? If the root
(basically /etc, /lib and a wholelotta mount points) is a
partition and your primary swap is also then you can boot just
as easily without LVM as with it. I've been running with / on
a 128MB partition for years and never pushed it past 50%. Same
for /var: adding a few choice mount points can reduce the need
for expanding the main storage enormously. If /var/log, for
example, is on a partition it makes life easier trying to
diagnose any problems.


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

Even luckier than that if they're patched to exactly the
same level you are and can read your LVM system. This only
has to blow up once before you get to spend a weekend [or
worse] fixing the problem.



--
Steven Lembark                               2930 W. Palmer
Workhorse Computing                       Chicago, IL 60647
                                            +1 800 762 1582

  reply	other threads:[~2001-11-21 20:32 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
2001-11-21 20:32     ` Steven Lembark [this message]
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=46460000.1006374706@dizzy \
    --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.