If we select the 4TB device/drive and then select "Maximum available space" (under Formatting) which shows the current partition format as "MBR", and we select "Use Free Space" (which currently shows two partitions, one is 465.75GB and the second partition is "free space" and shows 3.18TB of free space).
If we select "Use 'Free space' " then click the Next button, and when we get to the "Formatting" (Capacity) screen, it shows the maximum available space as 1582.25GB (exactly HALF of what the actual free space is).
For some reason it always shows the maximum available space (for Disk/LUN formatting) as HALF of what the physical space available on the hard drive is.
Is this a VMWare vSphere Client 5.5.0b bug? Or an ESXi 5.5.0 bug?
If we go back and select "Use all available partitions" (instead of "use 'Free space'), you would think that we could now use all 3.6TB (4TB) of available disk space.
Instead, it changes the partition format (from MBR to GPT) and now the Capacity is 3.64TB (4TB) but when you select "Use all available partitions" then click "next" when it gets to the "Disk/LUN - Formatting" page it says that the maximum available space is 2048GB, instead of 1582.25GB (which is far less than the 3.64TB of capacity). Is the vSphere 5.5.0b Client broken?
The 4TB hard drives are being recognized as 4TB (3.6TB) hard drives, but the vSphere Client is not allowing us to create a 4TB (3.6TB) datastore using VMFS-5.
We are using vSphere Client v5.5.0b (Build 1474107) and ESXi 5.5.0 (Build 1331820).
Any ideas as to how to fix this and create/format a 4TB (3.6TB) datastore using the vSphere Client?