From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] calculating free capacity from pvdisplay and lvdisplay
Date: Wed, 11 Aug 2010 12:19:50 -0500 [thread overview]
Message-ID: <1281547190.5708.0@raydesk1.bettercgi.com> (raw)
In-Reply-To: <AANLkTimUB-xWqJEteT6mvpLQ2Y4y1qGdGYK1LTz-bh=F@mail.gmail.com> (from rpnabar@gmail.com on Wed Aug 11 12:03:39 2010)
> Makes sense! The only reason that I was confused was why 3 of my PV's
> say "yes (but full)" and the other three not. How does one explain
> that?
>
> 1.63x3=4.89 still less than 8.6.
>
> Has the VG spanned across the first 3 PVs fully and then utilized the
> remaining 3 partially?
Pretty much. See man (8) lvm, --alloc option
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On 08/11/2010 12:03:39 PM, Rahul Nabar wrote:
> On Wed, Aug 11, 2010 at 1:10 AM, Ray Morris <support@bettercgi.com>
> wrote:
>
> Thanks Giorgio and Ray! That helps!
> >
> > df shows that your LVs take up 8.6TB: 6TB + 600 GB + 2 TB.
> > Therefore, you are using 8.6TB of disk space for those LVs.
> > Some of the space WITHIN each LV might not be used for files,
> > but it has been dedicated to that LV.
>
> Makes sense! The only reason that I was confused was why 3 of my PV's
> say "yes (but full)" and the other three not. How does one explain
> that?
>
> 1.63x3=4.89 still less than 8.6.
>
> Has the VG spanned across the first 3 PVs fully and then utilized the
> remaining 3 partially?
>
>
> > I'm not good at explaining things, so sometimes I try explaining
> three
> > different ways. �I have six cereal boxes, each half empty. �I put
> the
> > boxes in a bag. �The bag is now full. �The cereal boxes may not be
> full,
> > but they fill up the bag. �The cereal boxes are your half empty LVs
> and
> > the bag is your drives.
>
> Food based analogies are always good! :)
>
> Giorgio:
>
> The vgs output is exactly as you say:
>
> [root@eustorage ~]# vgs
> VG #PV #LV #SN Attr VSize VFree
> euclid_highperf_storage 6 3 0 wz--n- 9.80T 1.22T
>
> --
> Rahul
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
next prev parent reply other threads:[~2010-08-11 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 2:25 [linux-lvm] calculating free capacity from pvdisplay and lvdisplay Rahul Nabar
2010-08-11 6:10 ` Ray Morris
2010-08-11 17:03 ` Rahul Nabar
2010-08-11 17:19 ` Ray Morris [this message]
2010-08-11 8:42 ` Giorgio Bersano
-- strict thread matches above, loose matches on Subject: below --
2010-08-11 22:26 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
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=1281547190.5708.0@raydesk1.bettercgi.com \
--to=support@bettercgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.