linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: David Timms <dtimms@iinet.net.au>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] grow lv bug - pvs -v display bug
Date: Sat, 26 Sep 2009 01:12:44 +1000	[thread overview]
Message-ID: <4ABCDDEC.8000707@iinet.net.au> (raw)
In-Reply-To: <20090921223257.GB22590@us.ibm.com>

On 09/22/2009 08:32 AM, malahal@us.ibm.com wrote:
> Hugh [whobedobe@dodo.com.au] wrote:
>>      Scanning for physical volume names
>>    PV         VG         Fmt  Attr PSize  PFree  DevSize PV UUID
>>    /dev/sdb2  VolGroup00 lvm2 a-   67.91G 20.00G  47.93G eCuGyH-jV7L-Tgdg-JyYW-
>> sWK1-ehZY-OLw0WS
>
> DevSize is smaller than PSize!
Exactly what I was saying, yes PFree is indicating +'ve 20GB free, not 
-'ve 20GB Free. Looks at the very least like a bug in pvsc -v

I am guessing that my gui tool system-config-lvm uses the lvs PFree 
value to suggest that it can expand an lv into pv free space. But if 
this value was correct (ie showing as negative), then maybe it wouldn't 
suggest that there is pv free space, and then fail inexplicably when the 
user attempts to use some of that "anti-free" space ?

As well as displaying "-" space free, it might make sense for the tool 
to suggest there is something wrong with the setup, since the printed 
values don't actually make any sense (eg like assert (pvsize - pvusage) 
<> pvfree) to push the admin to see the problem.

DaveT.

      parent reply	other threads:[~2009-09-25 15:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-21 22:08 [linux-lvm] grow lv bug Hugh
2009-09-21 22:32 ` malahal
2009-09-21 22:47   ` Alasdair G Kergon
2009-09-22 13:16     ` Hugh
2009-09-22 13:23       ` Alasdair G Kergon
2009-09-22 21:55         ` Hugh
2009-09-22 22:27           ` Alasdair G Kergon
2009-09-25 15:12   ` David Timms [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=4ABCDDEC.8000707@iinet.net.au \
    --to=dtimms@iinet.net.au \
    --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).