From: Patrick Caulfield <caulfield@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] *** ANNOUNCEMENT *** LVM 1.0.4 available at www.sistina.com
Date: Tue May 21 01:53:01 2002 [thread overview]
Message-ID: <20020521065251.GB1035@tykepenguin.com> (raw)
In-Reply-To: <1021940894.3438.20.camel@pslgregory>
On Mon, May 20, 2002 at 05:28:10PM -0700, Gregory Ade wrote:
> On Thu, 2002-05-02 at 14:58, AJ Lewis wrote:
> > To clarify, this is a stable release with bugfixes for 1.0.3 only. Try LVM2
> > if you want to track the latest developments in LVM.
> >
> > LVM 1.0.4 supports both version 1 and 2 of the metadata.
> >
> > There's *no* need to run any metadata update tools.
>
>
> So, just to be sure, if I have a system that is running LVM 0.91.beta-7,
> I can install LVM 1.0.4 without worries?
Yes you can.
> I'm running a SuSE 7.2 install, which uses that version of LVM & their
> own SuSE-fied kernel rpm, but due to other requirements, I'm going to
> need to compile my own kernel from virgin sources. I'm going to be
> building 2.4.18, specifically with the linux-abi (formerly known as
> iBCS) patch, and figured I'd update everything with the latest LVM code
> while I was at it. I also remembered that I need the VFS-lock patch,
> since I want to do snapshots and we're running ReiserFS.
>
> Anything I need to beware of, before doing this?
Yes, beware that I screwed up with the VFS lock patch and the wrong one is in
the 1.0.4 tarball - get the right one from here:
http://tech.sistina.com/cgi-bin/cvsweb.cgi/~checkout~/LVM/PATCHES/linux-2.4.18-VFS-lock.patch?rev=1.1
patrick
prev parent reply other threads:[~2002-05-21 1:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 16:56 [linux-lvm] *** ANNOUNCEMENT *** LVM 1.0.4 available at www.sistina.com AJ Lewis
2002-05-03 4:11 ` Patrick Caulfield
2002-05-20 19:29 ` Gregory Ade
2002-05-21 1:53 ` Patrick Caulfield [this message]
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=20020521065251.GB1035@tykepenguin.com \
--to=caulfield@sistina.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox