Red Hat Bugzilla – Bug 750683
vol-info get the wrong "Type" for a directory
Last modified: 2013-10-20 17:44:15 EDT
Description of problem: [storage] vol-info get the wrong "Type" for a directory Version-Release number of selected component (if applicable): libvirt-0.9.4-20.el6.x86_64 qemu-kvm-0.12.1.2-2.206.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1） check the default pool , pool-dir is a dir # ll /var/lib/libvirt/images/ total 8006276 -rw-r--r--. 1 root root 503 Oct 31 15:47 i.sh drwx------. 2 root root 4096 Oct 31 13:24 pool-dir -rw-------. 1 root root 11928064 Nov 1 09:54 q2.img -rw-------. 1 qemu qemu 8589934592 Nov 1 15:31 t62.img drwx------. 2 root root 4096 Oct 31 13:22 test -rw-------. 1 qemu qemu 4482727936 Nov 1 15:31 test.img -rw-r--r--. 1 qemu qemu 358400 Oct 31 15:13 t.iso 2)get the info via vol-info command ,“Type” = block is incorrect. # virsh vol-info --pool default pool-dir Name: pool-dir Type: block Capacity: 0.00 Allocation: 0.00 Actual results: show wrong type of dir Expected results: show correct type of dir Additional info: vol-dumpxml can get the type it dir ... <format type='dir'/> ...
This bug can be reproduced with libvirt-0.9.4-21.el6.x86_64 qemu-kvm-0.12.1.2-2.207.el6.x86_64
This already fixed by upstream commit 9981fc5828f594.
Verified the bug with: libvirt-0.9.9-1.el6.x86_64 qemu-kvm-0.12.1.2-2.209.el6_2.1.x86_64 Steps: 1.Check the default pool, test-dir is a dir # ll /var/lib/libvirt/images total 39008240 -rwxrwxrwx. 1 qemu qemu 6442450944 Jan 10 01:30 rhel6.img -rw------- 1 root root 5242880000 Dec 30 05:27 rhel6u1-64b-hv.img drwxrwxrwx. 2 root root 4096 Nov 7 03:23 test drwxrwxrwx 2 root root 4096 Dec 30 22:12 test-dir -rwxrwxrwx. 1 root root 6784221696 Nov 16 15:07 test-preallocate-qcow2 -rwxrwxrwx. 1 root root 262144 Nov 6 22:18 vol-new.qcow2 -rwxrwxrwx. 1 qemu qemu 21474836480 Jan 4 02:35 win2008-x86_64.img 2.Get the info via vol-info command # virsh vol-info --pool default test-dir Name: test-dir Type: dir Capacity: 0.00 Allocation: 0.00
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0748.html