From: zoo1@corecomm.net
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Upgrading...
Date: Thu, 22 Feb 2001 18:13:00 -0500 [thread overview]
Message-ID: <20010222181300.A29027@bar.nowhere> (raw)
In-Reply-To: <20010222134043.B5285@omnifarious.mn.org>; from hopper@omnifarious.mn.org on Thu, Feb 22, 2001 at 01:40:43PM -0600
[-- Attachment #1: Type: text/plain, Size: 2204 bytes --]
On Thu, Feb 22, 2001 at 01:40:43PM -0600, Eric M. Hopper wrote:
> I have on _old_ version of LVM (0.8i). I don't do anything
>fancy with it. Only a few logical volumes and one volume group and
>striping across a couple of disks. Standard 4M block size. No
>mirroring, no snapshots. I do use reiserfs.
> This is under the 2.2.16 kernel.
> What problems, if any, should I expect if I upgrade to 2.4.2?
i'm in a similar situation myself, sitting on a late 2.4.0-pre kernel
with 0.8something waiting for a good time to upgrade.
now, i don't actually _know_ what your problems will be, since i'm not a
developer and really not very expert with LVM. but as far as i have
gathered from reading this list a while:
- your old 0.8 tools will not work with the new LVM in the new kernel;
- the tools you'll have to upgrade to won't work with the LVM code in
your old kernel, so once you upgrade the tools all you'll be able to
do (as far as LVM goes) is boot the new kernel and hope for the best;
- the LVM data structures on your disk will work with the new code. the
new code will update them with some new stuff (UUIDs); whether the
thusly upgraded on-disk structures would work with old LVM code i
don't know, but i would guess it will.
- and a stock, fresh-from-Linus'-harddisk kernel may need LVM patches,
the official tree might not have quite all it should as far as LVM
goes, so downloading the latest LVM tarball and letting it patch your
new kernel sources before building your new kernel might be wise.
personally, i'm waiting for a situation where an official kernel will
have an officially sanctioned, stable and complete LVM version and an
official LVM toolset will be able to deal with my old kernel before i
upgrade. yes, i have a backup tape drive, and yes, i have the expertise
to take the plunge, but i simply do not have the time to fiddle around
in case something breaks, and i want this machine to keep on working.
--
PGP/GnuPG key (ID 1024D/BFE0D6D0) available from keyservers everywhere
"Everything I am today, I owe to people whom it is now too late
to punish."
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-02-22 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 19:40 [linux-lvm] Upgrading Eric M. Hopper
2001-02-22 23:13 ` zoo1 [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-23 10:13 [linux-lvm] upgrading NagyZ
2002-12-23 10:54 ` Patrick Caulfield
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=20010222181300.A29027@bar.nowhere \
--to=zoo1@corecomm.net \
--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