From: Joe Thornber <thornber@btconnect.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Kurt Garloff <garloff@suse.de>,
linux-lvm@sistina.com, lvm-devel@sistina.com,
linux-kernel@vger.kernel.org
Subject: Re: [linux-lvm] Re: *** ANNOUNCEMENT *** LVM 1.0 available at www.sistina.com
Date: Wed, 15 Aug 2001 21:06:22 +0100 [thread overview]
Message-ID: <20010815210622.A1221@btconnect.com> (raw)
In-Reply-To: <20010815175659.A29749@sistina.com> <20010815182548.U3941@gum01m.etpnet.phys.tue.nl> <20010815185005.A32239@sistina.com> <20010815190428.A11146@athlon.random>
In-Reply-To: <20010815190428.A11146@athlon.random>; from andrea@suse.de on Wed, Aug 15, 2001 at 07:04:28PM +0200
On Wed, Aug 15, 2001 at 07:04:28PM +0200, Andrea Arcangeli wrote:
> On Wed, Aug 15, 2001 at 06:50:05PM +0200, Heinz Mauelshagen wrote:
> > offset. No known way around this.
>
> As said in the attached email (never got a reply about it yet btw)
> there's definitely a way around it, there's no magic in the beta7
> lvmtools, anything they can do can be done as well in the new lvmtools
> if we want to (and I believe we want to). I understand you don't want to
> clobber the core code with backwards compatibility cruft, but a new
> backwards compatibility utility, even in a new directory to make obvious
> nothing gets clobbered, could be developed and it would solve the
> problem.
I'm sorry I didn't reply to you Andrea, I didn't mean to be
disrespectful, but I didn't seem to be able to make my position
clear. Let me try again:
In previous beta releases of LVM the PE position was always being
calculated, rather than calculated upon PV creation and put in the
metadata. I was not aware of this.
This calculation varied through the beta series, it was based on some
constants that I changed (eg, SECTOR_SIZE which I changed to support
rawio), and constants that other people changed. This means that
different betas have PE's at different places.
The correct solution to this (IMO) is to add the missing pe_start
field to the metadata.
>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.
Should beta8 code go into the kernel ? possibly not. I think this could cause
people a lot of trouble if they are not familiar with the issues.
Should we have made the change ? yes. If you *do* care you can choose
to upgrade.
- Joe
next prev parent reply other threads:[~2001-08-15 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:56 *** ANNOUNCEMENT *** LVM 1.0 available at www.sistina.com Heinz J . Mauelshagen
2001-08-15 16:25 ` Kurt Garloff
2001-08-15 16:50 ` Heinz J . Mauelshagen
2001-08-15 17:04 ` Andrea Arcangeli
2001-08-15 20:06 ` Joe Thornber [this message]
2001-08-15 20:16 ` [linux-lvm] " Andrea Arcangeli
2001-08-15 20:20 ` [lvm-devel] " Christoph Hellwig
2001-08-15 21:19 ` Andrea Arcangeli
2001-08-15 17:19 ` Kurt Garloff
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 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=20010815210622.A1221@btconnect.com \
--to=thornber@btconnect.com \
--cc=andrea@suse.de \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@sistina.com \
--cc=lvm-devel@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