Soliciting feature requests for development of an LVM library / API

Dave Wysochanski dwysocha at
Fri Dec 12 17:30:38 PST 2008

David Z, Kay,

Thanks for your emails last week.  I'm working through them.  Ok, so
maybe what you need does not really apply to an LVM library, but you
need some LVM features.  Let's focus on scanning a PV for basic
information when a device is added.

On Fri, 2008-12-05 at 17:20 +0100, Kay Sievers wrote:
>   - dm/LVM tools export information about dm/LVM devices
>      in <KEY>=<value>\n format, not other format will work

I'm assuming by this, you're meaning something similar to what David
mentioned in his email about the information that is today available in
pvdisplay (or pvs) - you want that info in the udev database.

Does this BZ capture all that you need?

Note that by scanning a single PV we may not be able to answer
definitively what VG it is in or what LVs it may contain.  So provided
we go this route with putting into the udev database all needed
information that today you get from pv/vg/lvdisplay commands, something
else will have to put together individual PV information to get an
accurate picture of the VG / LV info in the system.

More information about the devkit-devel mailing list