<div dir="ltr">Actual size is the size that is actually allocated in the disk, if you create a thin provisioned 20GB disk for instance its actual size before installing an OS on it will be 0 bytes, after installing the OS it's expected to have a value in the actual size</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 20, 2017 at 7:45 PM, Jakub Niedermertl <span dir="ltr"><<a href="mailto:jniederm@redhat.com" target="_blank">jniederm@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Tal,<br>
<br>
what describe values in column 'actual_size' of view 'all_disks_for_vms'?<br>
<br>
I noticed very strange behavior of values in this column: It's<br>
* 0 for 'thin-provisioned' disk of VM in cluster 4.1<br>
* <a href="tel:2147487744" value="+12147487744">2147487744</a> for 'preallocated' 2GB disk of VM in cluster 4.1<br>
* 0 for 'thin-provisioned' disk of VM in cluster 4.0<br>
* 0 for 'preallocated' disk of VM in cluster 4.0<br>
* 0 for disk of template that was created by importing glance image as<br>
template to 4.0 cluster<br>
* 200704 for disk of template that was created by importing 12 MB<br>
glance image as template to 4.1 cluster<br>
* 0 for disk of template that was created by importing glance image as<br>
template to 4.0 cluster<br>
* 0 for disk of template of VM with preallocated disk in 4.1 cluster<br>
* 0 for disk of template of VM with preallocated disk in 4.0 cluster<br>
<br>
How is the value supposed to be computed?<br>
<br>
Thanks for explanation<br>
<span class="HOEnZb"><font color="#888888"><br>
Jakub<br>
</font></span></blockquote></div><br></div>