From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Re: *** ANNOUNCEMENT *** LVM 1.0 available at www.sistina.com
Date: Thu, 16 Aug 2001 11:05:26 +0100 [thread overview]
Message-ID: <20010816110526.A452@btconnect.com> (raw)
In-Reply-To: <20010815152432.A27984@omnifarious.org>; from hopper@omnifarious.org on Wed, Aug 15, 2001 at 03:24:32PM -0500
On Wed, Aug 15, 2001 at 03:24:32PM -0500, Eric M. Hopper wrote:
> On Wed, Aug 15, 2001 at 09:06:22PM +0100, Joe Thornber wrote:
> >
> > From looking at the metadata I have no way of knowing which version of
> > software the PV was created with. This is a sorry state of affairs,
> > but sadly true. So the upgrade script does the following:
> >
> > o interrogate the existing tools that created the PV to find where they put
> > the PE's
> >
> > o write this value into the new field.
> >
> > At this point the new driver, and tools should be installed.
>
> So, has the metadata also been updated to have a version number
> field in an easily found location? This is a very unpleasant state of
> affairs, and it will happen again if you haven't done this.
The metadata has always had a version number field. This is a single
integer field rather than a major/minor/patchlevel triplet which I
would prefer. This field used to be set to 1, and is now set to two
since the extra field was added. The real problem was that the
metadata format wasn't self consistent, it didn't tell you everything
you needed to know, there was 'magic' in the tools.
> This helps my peace of mind about doing the upgrade. Perhaps
> now I will do it with confidence that it will work and I'll get the
> order of operations right.
Read the instructions and follow the steps carefully and you should
have no trouble.
>
> One question I have:
>
> Does it hurt for the old drivers to be in the kernel at the time
> you run the upgrade script if none of the VGs are 'active'?
Let's see ... I think the old drivers do need to be present, so if
necessary a dummy LV can be created on empty PV's in order to get
pvdisplay to show the location of the start PE. Yes.
> I compiled LVM into my kernel instead of leaving it as a module,
> so if it were a problem, I'd have to compile a new kernel that didn't
> have the drivers.
If I were you I'd have builds of both the old and new kernel/tools
ready before you start.
- Joe
next prev parent reply other threads:[~2001-08-16 10:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:56 [linux-lvm] *** ANNOUNCEMENT *** LVM 1.0 available at www.sistina.com Heinz J . Mauelshagen
2001-08-15 15:56 ` Heinz J . Mauelshagen
2001-08-15 16:25 ` [linux-lvm] " Kurt Garloff
2001-08-15 16:25 ` Kurt Garloff
2001-08-15 16:50 ` [linux-lvm] " Heinz J . Mauelshagen
2001-08-15 16:50 ` Heinz J . Mauelshagen
2001-08-15 17:04 ` [linux-lvm] " Andrea Arcangeli
2001-08-15 17:04 ` Andrea Arcangeli
2001-08-15 17:21 ` [linux-lvm] " Eric M. Hopper
2001-08-15 20:06 ` Joe Thornber
2001-08-15 20:06 ` Joe Thornber
2001-08-15 20:16 ` Andrea Arcangeli
2001-08-15 20:20 ` [lvm-devel] " Christoph Hellwig
2001-08-15 21:19 ` Andrea Arcangeli
2001-08-15 20:24 ` Eric M. Hopper
2001-08-16 10:05 ` Joe Thornber [this message]
2001-08-15 17:19 ` Kurt Garloff
2001-08-15 17:19 ` Kurt Garloff
2001-08-17 9:16 ` [linux-lvm] " Heinz J . Mauelshagen
2001-08-17 10:23 ` Kurt Garloff
2001-08-17 14:56 ` Heinz J . Mauelshagen
2001-08-15 17:55 ` Andreas Dilger
2001-08-15 17:55 ` Andreas Dilger
2001-08-15 20:13 ` [linux-lvm] " Joe Thornber
2001-08-15 21:13 ` Andrea Arcangeli
2001-08-15 21:13 ` Andrea Arcangeli
2001-08-16 10:08 ` [linux-lvm] " Joe Thornber
2001-08-15 19:14 ` Hubert Mantel
2001-08-15 19:14 ` Hubert Mantel
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=20010816110526.A452@btconnect.com \
--to=thornber@btconnect.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.