On Fri, Aug 16, 2013 at 08:08:07PM +0800, Osier Yang wrote:
> RHEL6.5:
https://bugzilla.redhat.com/show_bug.cgi?id=965442
>
> One has to refresh the pool to get the correct pool info after
> adding/removing/resizing a volume, this updates the pool metadata
> (allocation, available) after those operation are done.
I didn't look more closely but it seems this broke libvirt-tck:
http://honk.sigxcpu.org:8001/job/libvirt-tck-debian-wheezy-qemu-session/1...
If you look at the libvirtd.log
http://honk.sigxcpu.org:8001/job/libvirt-tck-debian-wheezy-qemu-session/1...
the volume name looks rather weird:
info : storageVolDelete:2379 : Deleting volume '8Ü!¹àÂ,¹@' from storage pool
'tck'
after this patch got applied.
Yep, this is caused by the issue Jan pointed out in his reply. We're
free'ing data that is still in use.
Daniel
--
|: