From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: master - lvm2app: lvm_vg_list_lvs filter hidden LVs
Date: Wed, 24 Jul 2013 00:41:56 +0200 [thread overview]
Message-ID: <51EF06B4.5030804@redhat.com> (raw)
In-Reply-To: <51EEE05C.4080805@redhat.com>
Dne 23.7.2013 21:58, Tony Asleson napsal(a):
> On 07/23/2013 02:27 PM, Zdenek Kabelac wrote:
>> Dne 23.7.2013 21:03, tasleson napsal(a):
>>> Gitweb:
>>> http://git.fedorahosted.org/git/?p=lvm2.git;a=commitdiff;h=a2b51476007aae91acfc121a7fd2ce04f3b08781
>>>
>>> Commit: a2b51476007aae91acfc121a7fd2ce04f3b08781
>>> Parent: 31de670318c9794690601468def392cd7e4eb0fc
>>> Author: Tony Asleson <tasleson@redhat.com>
>>> AuthorDate: Tue Jul 23 14:57:53 2013 -0400
>>> Committer: Tony Asleson <tasleson@redhat.com>
>>> CommitterDate: Tue Jul 23 14:01:20 2013 -0500
>>>
>>> lvm2app: lvm_vg_list_lvs filter hidden LVs
>>>
>>> The function lvm_vg_list_lvs was returning all logical
>>> volumes, including *_tmeta and *_tdata. Added check
>>> to verify that LV is visible before including in list
>>> of returned logical volumes.
>>
>> I'm afraid you can't break API this way.
>> If there is a need for filtered list - you need to filter
>> list passed from this function - or add something like
>> lvm_vg_list_visible_lvs.
>
> What kind of modifications are users doing to the hidden meta-data/data
> components of a LV thin pool that they would reference each part
> individually?
i.e. you could convert _tmeta into mirror.
And there are other hidden volumes which could be legally removed.
Zdenek
prev parent reply other threads:[~2013-07-23 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 19:03 master - lvm2app: lvm_vg_list_lvs filter hidden LVs tasleson
2013-07-23 19:27 ` Zdenek Kabelac
2013-07-23 19:58 ` Tony Asleson
2013-07-23 22:41 ` 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=51EF06B4.5030804@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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.