From: Terje Kvernes <terjekv@math.uio.no>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Red Hat upgrade over existing LVM
Date: Sat Apr 6 02:28:02 2002 [thread overview]
Message-ID: <wxxsn69ut5v.fsf@nommo.uio.no> (raw)
In-Reply-To: <3CAE9F23.3C58CB1E@vtc.edu.hk>
Nick Urbanik <nicku@vtc.edu.hk> writes:
> We have a number of servers with /usr and /var on LVM. The
> difficulty arises when upgrading from one version of Red Hat to
> another; the installation disks do not recognise the logical
> volumes.
a well known issue.
> Do any of you have any reasonable approach to solving this?
if you want to do the "normal" thing with a CD-boot-upgrade, no,
you're fscked.
> Do I need to create a new network installation boot disk with a
> small kernel with support for LVM and scripts to turn on LVM groups?
that's one way, the easier way is to either use apt or red-carpet to
upgrade your distro. with red-carpet, fiddle with
/etc/redhat-release, apt has dist-upgrade, I think. I've upgraded
two machines from 7.0 -> 7.2 with red-carpet, but I'd advice you to
set off a day with this, even if you get the rpms from somewhere
besides ximian.
I did it as follows: grab the rpms from RH7.2, with the updates,
from a local mirror, and dump them to /var/cache/redcarpet, then
fiddle with /etc/redhat-release (feel free to install the rpm
"redhat-release"), then run red-carpet. things will break and fail
now and then, fiddle.
these days I have a RH7.2-box that has an uptime of about 240 days.
:)
--
Terje
next prev parent reply other threads:[~2002-04-06 2:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 1:08 [linux-lvm] Red Hat upgrade over existing LVM Nick Urbanik
2002-04-06 2:28 ` Terje Kvernes [this message]
2002-04-06 15:30 ` Steve Wray
2002-04-06 21:26 ` Terje Kvernes
2002-04-08 2:54 ` Remco Post
2002-04-06 22:47 ` Nick Urbanik
2002-04-06 23:45 ` Steve Wray
2002-04-08 4:04 ` Eduard Bloch
2002-04-06 22:44 ` Nick Urbanik
2002-04-06 23:13 ` Terje Kvernes
2002-04-07 5:28 ` Luca Berra
2002-04-08 2:07 ` Dirk Heinrichs
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=wxxsn69ut5v.fsf@nommo.uio.no \
--to=terjekv@math.uio.no \
--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