Been Apple'ed

[ChipMcK]

When a virtual hard drive is created, you ask for a size and set that value as its size.

When I boot up a virtual machine and start up its Disk Management (Disk Utility, GPARTED, etc.}, i find a  different size,  70 GB is now 75+ GB.  Over the years, this has been written off as 10-based math versus 2-based math.

Now, Apple, in its infinite “Listen, stupid, I know what you want, if even you have not asked for it” largess, has decided that file and partition sizes shall be 10-based.  This difference of opinion/method  is making space management difficult.

Some thoughts on the matter?

[chstueben]

I am sure this problem will last for the next 1000 years.

Ahem, sorry, for the next 1024 years :smileylaugh:

greetings from germany

Chris

[Technogeezer]

You are somewhat correct in that this is a base-2 vs base-10 issue, but the true problem is a misuse of the prefix "GB" by Fusion.

OS X, Linux and disk drive manufacturers are correctly using the SI prefix GB as 10^6 bytes. Windows and (apparently) VMware incorrectly refer to a GB as 2^30 or 1024^3 bytes, when they should be reporting 1024^3 bytes as the ISO/IEC binary prefix "gibibytes" (GiB). 

What I think may be happening when you tell Fusion to create a 70 "GB" virtual disk is it actually created a 70 GiB virtual disk (70 x 1024^3 bytes). If you do the math 70 GiB is approximately 75 GB - which is what Disk Utility and Gparted are reporting.

If this is indeed the case, one would think Fusion should be changed to properly use the prefix GiB so that it is unambiguous in the size of the disk it is creating.

I bet that Windows disk management will report 70 "GB".