https://bugzilla.redhat.com/show_bug.cgi?id=1166592
More recent versions of LVM have resulted in the inability to recognize
a newly created thin logical volume using libvirt. Not sure exactly which
lvm release resulted in the change, but it's some time between 2.02.106 and
2.02.113 or lvm library version 1.02.85 and 1.02.92.
The short story is libvirt was not really creating thin logical volumes,
instead libvirt was creating thin snapshot logical volumes. More recent
changes in LVM seem to now differentiate the two and the way libvirt was
creating it's logical volumes "now defaulted" to the thin logical volume,
which libvirt was not able to parse properly.
The commit message for patch 1 has the gory details - figured it was best
to keep it in the commit message rather than be lost to some cover letter.
The second patch adds the ability to get the allocation and capacity for
logical volumes from a volResize callback. This will be important for
the thin logical volumes in order to determine the capacity which is stored
in the thin logical volume pool
John Ferlan (2):
logical: Use correct syntax for thin/sparse pool creation
logical: Introduce virStorageBackendLogicalRefreshVol
src/storage/storage_backend_logical.c | 216 +++++++++++++++++++++++++++++++---
src/util/virstoragefile.h | 1 +
2 files changed, 199 insertions(+), 18 deletions(-)
--
1.9.3