linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Jonathan Brassow <jbrassow@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Concise LVM Summary
Date: Wed, 12 Apr 2006 10:59:08 -0500	[thread overview]
Message-ID: <1144857548.16665.7.camel@hydrogen.msp.redhat.com> (raw)
In-Reply-To: <20060412041706.36220.qmail@web60419.mail.yahoo.com>

On Tue, 2006-04-11 at 21:17 -0700, linux_user98765@yahoo.com wrote:
> lvs,pvs,vgs each provide for output of specified columns (with optional
> headers and field separators); HOWEVER this is still limited as (at
> least on my debian pkg) PV and LV commands cannot be combined, thus
> negating the possibility of anything even as simple as:

Of course, but you said you were using a perl script to put the info
together.  Using the commands as suggested makes them easier to parse.

You should be able to figure out how full a PV is that is part of an LV,
but I'm not sure you can determine what parts of a pv an lv uses - or
how much space an lv uses of a pv.

For example:
prompt> lvs --noheadings -o devices vg/lv
  /dev/sda(0)
  /dev/sdb(0)
prompt> pvs --noheadings -o pv_used,pv_size /dev/sda
  17.15G 17.15G

So, you can use vgs to get the vg names, lvs to get the lv names in
those vgs and the devices they live on, and pvs to get basic usage.

If you want to do more, you might consider looking
at /etc/lvm/backup/<vg name>

 brassow

      reply	other threads:[~2006-04-12 15:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-08 21:11 [linux-lvm] Concise LVM Summary linux_user98765
2006-04-10  8:08 ` Thomas Meller
2006-04-11 15:00 ` Jonathan E Brassow
2006-04-12  4:17   ` linux_user98765
2006-04-12 15:59     ` Jonathan Brassow [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=1144857548.16665.7.camel@hydrogen.msp.redhat.com \
    --to=jbrassow@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).