linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Gabriel <jarod125@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] show free space _inside_ logical volume
Date: Tue, 1 Dec 2009 02:45:56 +0200	[thread overview]
Message-ID: <4cd59bf50911301645l51c44579k978225d3fe9e71b0@mail.gmail.com> (raw)

Hi all,

I'm interested to know if it is possible to check the amount of free
space _inside_ a LV. I know that usually a LV is fully "occupied" by a
partition, but there is a (short) period when there is a gap between
the size of the partition and the size of the LV it resides on. That
happens _after_ doing a lvextend and _before_ doing the resize
(expand) of the filesystem.

First thing I thought of was lvdisplay. While I can see how many LEs
the LV has, I cannot see how many of them are in use by the filesystem
and how many are free (the way pvdisplay shows total/free/allocated
PEs).

It was suggested to me that I try some filesystem tools (resize2fs,
dumpe2fs, tune2fs etc.) that might show me the free space. resize2fs
does not have a 'dry-run' option that would have shown the new size
(in blocks) of the filesystem and I didn't find anything useful in
tune2fs' manual either.

dumpe2fs shows various information such as block count, free blocks
and block size, but I see no modifications when running this before
and after the lvextend command.

I also tried parted -l, but to no avail.

             reply	other threads:[~2009-12-01  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-01  0:45 Gabriel [this message]
2009-12-01  8:17 ` [linux-lvm] show free space _inside_ logical volume Lyn Rees
2009-12-01 18:28 ` Mark H. Wood
2009-12-01 18:33   ` Stuart D. Gathman
2009-12-02 22:36     ` Gabriel

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=4cd59bf50911301645l51c44579k978225d3fe9e71b0@mail.gmail.com \
    --to=jarod125@gmail.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).