From: Peter Rajnoha <prajnoha@redhat.com>
To: lvm-devel@redhat.com
Subject: "lv_attr" disappeared from lvm_lv_get_property?
Date: Fri, 30 Jan 2015 10:42:43 +0100 [thread overview]
Message-ID: <54CB5213.7030108@redhat.com> (raw)
In-Reply-To: <87mw50ipfv.fsf@red.mvo.lan>
On 01/30/2015 10:32 AM, Marius Vollmer wrote:
> Peter Rajnoha <prajnoha@redhat.com> writes:
>
>> Unfortunately, this was a regression introduced in LVM2 v115. It should
>> be fixed now (https://bugzilla.redhat.com/show_bug.cgi?id=1187481#c2).
>
> Thanks! (I think there is more to do, unfortunately, see the bug.)
>
(yup, I'm looking at that now)
>> I wouldn't say lvm2app is unusable, it's just not as maintained and
>> refreshed as direct LVM tools. [...]
>
> Do you know of any users besides storaged?
>
Anaconda was one of the candidates to use liblvm, but afaik, they're
still forking LVM commands.
The other one I know of is the udisks, but it removed support for LVM
some time ago and udisks2 and later does not handle LVM anymore.
And then your use case :)
I don't know about more lvm2app users (but if anyone knows about more,
correct me) at the moment. That's also the reason why we (or I) don't
invest so much time into this and we spend this time on improving direct
LVM commands instead, I'd say.
> We should cooperate and make somehow sure that the storaged and Cockpit
> tests run for each LVM2 update...
...and we (LVM) should add more tests into our testsuite for the lvm2app.
--
Peter
next prev parent reply other threads:[~2015-01-30 9:42 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
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 [this message]
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=54CB5213.7030108@redhat.com \
--to=prajnoha@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.