Hello everyone! I would like to thank you all for the project and the
tool developed across these years. I am a fan of yours! This is very
important to make the new technology era a better and open place to
work and live with!
I´m facing a weird listing image file behaviour (or at least I think
It is), that have a 500GB Qcow2 image:
[root@server /]# qemu-img info /var/lib/libvirt/images/netvoltcloudserv.img
image: /var/lib/libvirt/images/netvoltcloudserv.img
file format: qcow2
virtual size: 500G (536870912000 bytes)
disk size: 489G
cluster_size: 65536
Format specific information:
compat: 1.1
lazy refcounts: true
- The Image size is 500GB, and that´s correct and exacly what I have set up.
Now the problem is when I ls this image:
[root@server /]# ls -la /var/lib/libvirt/images/
total 512593892
drwx--x--x. 4 root root 75 Set 16 22:46 .
drwxr-xr-x. 10 root root 117 Jun 20 12:04 ..
drwx--x--x. 2 root root 29 Jul 5 2018 discos_virtuais
-rwx--x--x. 1 qemu qemu 1010408555008 Set 25 11:51 netvoltcloudserv.img
drwx--x--x. 2 root root 6 Set 16 22:46 nsf-pool-1
- THE SIZE OF THIS IMAGE IS 1TB!
SO MY QUESTION BASED ON THIS, IS:
- Is this a "bug" or "expected" behavior?
- Who to "fix the size" or make SISOP see it correctly (with 500GB)?
Thank you in advance!
Regards
Julianno Nogueira
