Currently I found it it's hard to determine the relationship between
LVM objects, by which I mean "what PVs contain a VG?", or "what LVs
are contained in a VG?"
This simple API exposes that to callers.
{lv,vg,pv}uuid:
Return the UUID of an LVM object. You can already get this
using (eg.) lvs_full, but this is a lot less faffing around.
vg{lv,pv}uuids:
Return the LVs belonging to a VG, or the PVs containing a VG.
It returns them as UUIDs, so if you build up a map using the
previous calls, then you can map them back to names, or keep
them as UUIDs as required.
There's an example Perl program included which demonstrates how to do
this.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://et.redhat.com/~rjones/virt-top