From: Dave Wysochanski <dwysocha@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lv segment "devices" property?
Date: Wed, 08 Dec 2010 11:02:20 -0500 [thread overview]
Message-ID: <1291824140.6769.394.camel@f12-work> (raw)
In-Reply-To: <201012071901.01998.benscott@nwlink.com>
On Tue, 2010-12-07 at 19:01 -0800, ben wrote:
> Is there any plan to add the lvm2app get property "devices" function for
> logical volume segments?
>
> ie: value = lvm_lvseg_get_property(lvm_lvseg, "devices");
>
> Thank you.
> benscott@nwlink.com
>
Patches were posted on 11/22 here to address 'devices' and
'seg_pe_ranges':
https://www.redhat.com/archives/lvm-devel/2010-November/msg00091.html
Petr also recently committed patches to rework some internal 'percent'
code and I think will add the "snap_percent" and "copy_percent"
properties.
I suspect these are just part of the lvm-devel patch backlog and will
eventually get in.
prev parent reply other threads:[~2010-12-08 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 3:01 [linux-lvm] lv segment "devices" property? ben
2010-12-08 16:02 ` Dave Wysochanski [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=1291824140.6769.394.camel@f12-work \
--to=dwysocha@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).