From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bug in LVM2 tools
Date: Wed, 4 Oct 2006 23:28:24 +0100 [thread overview]
Message-ID: <20061004222824.GH17654@agk.surrey.redhat.com> (raw)
In-Reply-To: <4524222F.3060902@baldauf.org>
On Wed, Oct 04, 2006 at 11:05:51PM +0200, Xu�n Baldauf wrote:
> I observed an obscure bug in the current LVM2 tools. Observe this:
> # vgcreate --physicalextentsize=1k test.vg /dev/loop4
When you have larger PEs, this bug gets lost in the rounding that gets done
for alignment.
> It seems that there is
> space reserved for a second metadata copy at the end of /dev/loop4,
It's not actually related to that - it's simply a mistake in the logic that
means it adjusts for the metadata areas both in pvcreate and then a second
time in vgcreate. When you run vgremove it now reinstates the full disk
size (a bug fix that was applied) so the subsequent vgcreate only makes a
single (correct) adjustment. In short, there's confusion of responsibility
between pvcreate and vgcreate for calculating the usable data area size
that holds the PEs.
Alasdair
--
agk@redhat.com
prev parent reply other threads:[~2006-10-04 22:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 21:05 [linux-lvm] Bug in LVM2 tools Xuân Baldauf
2006-10-04 22:05 ` Alasdair G Kergon
2006-10-04 22:28 ` Alasdair G Kergon [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=20061004222824.GH17654@agk.surrey.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.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).