All of lore.kernel.org
 help / color / mirror / Atom feed
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:14:33 +0100	[thread overview]
Message-ID: <54CB4B79.8000005@redhat.com> (raw)
In-Reply-To: <87oapgiu3z.fsf@red.mvo.lan>

On 01/30/2015 08:51 AM, Marius Vollmer wrote:
> Alasdair G Kergon <agk@redhat.com> writes:
> 
>> Sounds like we forgot to update the library code to use the new method...
> 
> I filed a bug for this:
> 
>     https://bugzilla.redhat.com/show_bug.cgi?id=1187481
> 

Unfortunately, this was a regression introduced in LVM2 v115. It should
be fixed now (https://bugzilla.redhat.com/show_bug.cgi?id=1187481#c2).

> Let us know how we are going to fix this.  If lvm2app is really a lost
> cause, we can change storaged to fork lvs etc and parse it's output.

I wouldn't say lvm2app is unusable, it's just not as maintained and
refreshed as direct LVM tools. The bug above was just a silly regression
that happened (yes, we should add full test coverage to lvm2app - that's
currently missing, I admit).

Also, recently, we've added tons of new fields, also fields for
reporting each attribute in its own field so you have easier job
when parsing the output (see lvs/vgs/pvs -o help). However,
some of these new fields doesn't have lvm2app hooks yet written -
they're going to be added soon.
-- 
Peter



  reply	other threads:[~2015-01-30  9:14 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 [this message]
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=54CB4B79.8000005@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.