From: Joe Thornber <thornber@btconnect.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] LVM 0.9/1.0.x migration
Date: Fri Oct 19 07:40:02 2001 [thread overview]
Message-ID: <20011019134146.D644@btconnect.com> (raw)
In-Reply-To: <20011019122625.A25049@xlink.net>; from hadmut@danisch.de on Fri, Oct 19, 2001 at 12:26:25PM +0200
On Fri, Oct 19, 2001 at 12:26:25PM +0200, Hadmut Danisch wrote:
> Hi,
>
> I just have a question:
>
> I saw that README.1st and pvversion have vanished between
> 1.0 and 1.0.1-rcX.
>
> Does this mean that there is no way or no need to upgrade
> anymore? Any disadvantages with continuing to use the old
> version?
You no longer need to upgrade to version 2 data structures. Newer
releases understand both formats so there's no reason not to upgrade.
Newer releases will down grade any version 2 VG's it finds when you
next *change* the metadata (eg. resize an LV).
Version 2 was bogus and resulted from my not realising that
pv->pe_on_disk.size included all the blank space upto the first PE.
Making pv->pe_start redundant.
- Joe
prev parent reply other threads:[~2001-10-19 7:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 5:25 [linux-lvm] LVM 0.9/1.0.x migration Hadmut Danisch
2001-10-19 7:33 ` Heinz J . Mauelshagen
2001-10-19 7:40 ` Joe Thornber [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=20011019134146.D644@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).