linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] what is free space in LVM
Date: Tue, 14 Jul 2015 10:43:59 +0200	[thread overview]
Message-ID: <55A4CBCF.1050706@redhat.com> (raw)
In-Reply-To: <CAK9_OPrqjkfNhxtRUT8V6nuqxfB0jrLtRmipB0Q8LpNbxguAuw@mail.gmail.com>

Dne 10.7.2015 v 11:45 Angelo Moreschini napsal(a):
> Hi,
>
> I am new to LVM and I would like to have an exact answer to the question :
>
> what is the criteria that allows to distinguishes the "free space" on the all
> the space in a Volume Group?
>
> or (if you prefer)...
>
> howthe command pvscan does to obtain information about the free space in LVM ?
>
> ------------
> According to my current knowledge, I know that the definition of "free space"
> concerns with withthe set of blocks for which, in the FAT, is not  registered
> a significant link to access a file.
>
> But I think that in the context of LVM there should be a different criterion
> to define the "free space" insidea Volume Group.
> ----------

lvm2 is NOT filesystem

lvm2 is 'volume manager' - thus  every PV is divided into extents.
And 'extent' could be associated with LV.

So easily - if PV has  32bit #extent count.
(Size of extent is again 32bit number -> in total 64bit address space).

So when you calc all extents in use (being member of any LV),
and subtracts this from number of all available extent
you will get number of 'free' extent.

Note - you put filesystem ON your LV - and then filesystem is managing free 
space within this LV.

Zdenek

      parent reply	other threads:[~2015-07-14  8:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10  9:45 [linux-lvm] what is free space in LVM Angelo Moreschini
2015-07-13  7:52 ` Mauricio Tavares
2015-07-14  8:43 ` Zdenek Kabelac [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=55A4CBCF.1050706@redhat.com \
    --to=zkabelac@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).