From: Georges Giralt <georges.giralt@free.fr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Chicken and egg problem..
Date: Wed Nov 21 08:48:02 2001 [thread overview]
Message-ID: <1006354219.3bfbbf2b53adf@imp.free.fr> (raw)
In-Reply-To: <7510000.1006331425@dizzy>
En r�ponse � Steven Lembark <lembark@wrkhors.com>:
>
>
> -- 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.
Yes and no....
I use HP boxes, on which LVM is native.
My computer has been upgraded from RH4.1 to 7.1 with all the steps in beetween.
This is why I would use LVM on my boot disk.
Tired re creating a new / or /var and moving data from one file system to the
next.
And I always have bootable floppy/CD floating around...
My question was in fact to learn how to make the LVM information static on the
/etc directory. (if this information is not valid, the system will not boot
anyway, so it doesn't hurt) Of course, I must rebuild these files if I change
the volume group holding the / filesystem.... Something which is easyly done on
an HP machine...
>
> 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
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@sistina.com
> http://lists.sistina.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html
>
next prev parent reply other threads:[~2001-11-21 8:48 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 [this message]
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=1006354219.3bfbbf2b53adf@imp.free.fr \
--to=georges.giralt@free.fr \
--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