From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: "lv_attr" disappeared from lvm_lv_get_property?
Date: Thu, 29 Jan 2015 21:46:39 +0100 [thread overview]
Message-ID: <54CA9C2F.6090708@redhat.com> (raw)
In-Reply-To: <87pp9xibcz.fsf@red.mvo.lan>
Dne 29.1.2015 v 21:24 Marius Vollmer napsal(a):
>
> Alasdair G Kergon <agk@redhat.com> writes:
>
>> On Thu, Jan 29, 2015 at 09:50:08PM +0200, Marius Vollmer wrote:
>>> at one moment lvm_lv_get_property returned a valid and useful "lv_attr"
>>> property, and then suddenly it returns values with "is_valid == 0".
>>
>> The way some of the properties are gathered got changed.
>>
>> Sounds like we forgot to update the library code to use the new method...
>
> I found this:
>
> /* backward compatible internal API for lvm2api, TODO improve it */
> char *lv_attr_dup(struct dm_pool *mem, const struct logical_volume *lv)
>
> Guys, really. Write some tests.
>
Hi
lvm2api is rather purely experimental part of lvm2 - it has no real maintainer
and no real plans on further development ATM.
I'd strongly recommend to use lvm2 commands - since they are far more
optimized and tested.
lvm2api at current stage has huge list of hardly resolvable issues and some
new way has to be used to fix them (likely some 'client/server' model)
Regards
Zdenek
next prev parent reply other threads:[~2015-01-29 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 19:50 "lv_attr" disappeared from lvm_lv_get_property? Marius Vollmer
2015-01-29 20:03 ` Alasdair G Kergon
2015-01-29 20:24 ` Marius Vollmer
2015-01-29 20:46 ` Zdenek Kabelac [this message]
2015-01-30 7:51 ` Marius Vollmer
2015-01-30 9:14 ` Peter Rajnoha
2015-01-30 9:32 ` Marius Vollmer
2015-01-30 9:42 ` Peter Rajnoha
2015-01-30 9:54 ` Peter Rajnoha
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=54CA9C2F.6090708@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.