From: Malahal Naineni <malahal@us.ibm.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] calculating free capacity from pvdisplay and lvdisplay
Date: Wed, 11 Aug 2010 17:52:10 -0700 [thread overview]
Message-ID: <20100812005210.GA2963@us.ibm.com> (raw)
In-Reply-To: <AANLkTi=rOeVixFV6zD6uNZgLXh6zKR1oPBXDDHzNN9hE@mail.gmail.com>
Rahul Nabar [rpnabar@gmail.com] wrote:
> On Wed, Aug 11, 2010 at 6:56 PM, Malahal Naineni <malahal@us.ibm.com> wrote:
> >
> > It is 'normal' for VG and 'inherit' for an LV. See 'man lvm' command for
> > details. See 'man vgs' on how to get it. Allocation policy is part of vg
> > 'Attr' field. Look for Attr value when you run 'vgs -o+attr'
>
> THanks! I do have "normal" allocation policy on the VG and all the
> LV's inherit this.
> But that just deepens the mystery. Why are my first 3 PV's showing
> full and the others not?
I don't know your particular situation, but if you create an LV, it will
normally use the first PV. Until the first PV is used, it won't allocate
from the next PV. This is only true if you use linear LV. If you use
stripes, that allocation would be completely different.
I don't think LVM remembers the last used PV for allocation to use any
kind of round robin allocation among different lvcreates. Hope that
answers your mystery.
Thanks, Malahal.
next prev parent reply other threads:[~2010-08-12 0:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 22:26 [linux-lvm] calculating free capacity from pvdisplay and lvdisplay Daksh Chauhan
2010-08-11 22:40 ` Stuart D. Gathman
2010-08-11 23:01 ` Rahul Nabar
2010-08-11 23:56 ` Malahal Naineni
2010-08-12 0:22 ` Rahul Nabar
2010-08-12 0:52 ` Malahal Naineni [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-11 2:25 Rahul Nabar
2010-08-11 6:10 ` Ray Morris
2010-08-11 17:03 ` Rahul Nabar
2010-08-11 17:19 ` Ray Morris
2010-08-11 8:42 ` Giorgio Bersano
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=20100812005210.GA2963@us.ibm.com \
--to=malahal@us.ibm.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).