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 08:31:01 2001	[thread overview]
Message-ID: <7510000.1006331425@dizzy> (raw)
In-Reply-To: <1006347197.3bfba3bd23d95@imp.free.fr>


-- Georges Giralt <georges.giralt@free.fr>

> Hello !
> As I've previously said, I plan to make my RedHat 7.1 (kernel 2.4.5) a
> pure LVM  machine.
> To do so, I've build the 1.0.4 version of LVM into the kernel (with the
> NCR SCSI  driver). As to avoid an initrd. Simple is beautifull...
>
> In the sysinit rc script, Redhat has put a vg activation command, but....
> My kernel panics, as it is unable to mount root, as the LVM activation
> commands  are after the root fsck (and mount..)
>
> If I put the LVM activation lines early, in the sysinit script, these
> commands  complains beeing not able to access /etc/lvmtab....

The kernel panic is extactly why you probably wouldn't
want to use only LVM on the system. 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.

This is pretty much the only way you'll be able to
convienently recover from any LVM problems in the future.
Otherwise you'll need bootable media floating around.

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

  reply	other threads:[~2001-11-21  8:31 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 [this message]
2001-11-21  8:48   ` Georges Giralt
2001-11-21 12:36   ` Brian J. Murrell
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=7510000.1006331425@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.