Hello,
I'm trying to create a 2TB VMDK file for a VM on a ESXi 5.0 Update 1 (build 623860).
I know the max size is 2TB minus 512 bytes, but I thought it would be possible to select 2TB as the size and vSphere would remove the 512 bytes itself since it accepts the size. Higher than 2TB and you get an error and it adjusts itself to 2TB, like this:
But even though it creates the file without error, something fishy is going on... The first file were created at 2TB, the second at 2047GB, both thick.
As you can see the first one appears to be thin, but I've tried both lazy zeroed and eager zeroed with the same result.
The 2TB disk appers to be working fine, but vCenter adds an additional 2TB as uncommitted space, which cause a datastore overcommitted warning to go off, and I don't like warnings in my enviroment.
Any ideas to why this is happening at the 2TB mark?