[Engine-devel] storage overallocation ratio

Hi, I was trying to find out how is this actually calculated. Doesn't look very straightforward…:) I'm curious about the following - vdsm reports something like truesize and apparentsize which IIUC should be distinct but then in engine, in backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/irsbroker/GetImageInfoVDSCommand.java it's written to the same engine property actual_size. That doesn't sound right. Can someone enlighten me please? Thanks, michal

Hi Michal, apparentsize is the size that you perceive when working with the volume (i.e., ignoring sparseness etc.) while trusize is the size taken on the drive (i.e., taking sparseness etc. into account). DiskImage.getActualSize() should report the truesize. The end result is OK, since truesize overrides apparentsize in that command, but it's obviously wrong, and should be fixed [1]. [1] http://gerrit.ovirt.org/#/c/14176/ ----- Original Message -----
From: "Michal Skrivanek" <michal.skrivanek@redhat.com> To: engine-devel@ovirt.org Sent: Saturday, April 20, 2013 11:13:04 PM Subject: [Engine-devel] storage overallocation ratio
Hi, I was trying to find out how is this actually calculated. Doesn't look very straightforward…:)
I'm curious about the following - vdsm reports something like truesize and apparentsize which IIUC should be distinct but then in engine, in backend/manager/modules/vdsbroker/src/main/java/org/ovirt/engine/core/vdsbroker/irsbroker/GetImageInfoVDSCommand.java it's written to the same engine property actual_size. That doesn't sound right. Can someone enlighten me please?
Thanks, michal _______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
participants (2)
-
Allon Mureinik
-
Michal Skrivanek