Determine Disk Type eagerzeroedthick or zeroedthick

[mike-p]

I have to confirm that the system disk of a MCS-node is eagerzeroedthick.

In the clients ver. 5.5.0 Build 218311 and the webclient the disk is shown as lazy zeroed. I inflated the vmdk with vmfstools -D and got a 100% success message.

Neverthless the clients show both the disk as lazy zeroed.

I checked the disks according "Determining if a VMDK is zeroedthick or eagerzeroedthick (1011170)" and got this result :

Lock [type 10c00001 offset 205000704 v 193, hb offset 3522560 gen 109, mode 0,

owner 00000000-00000000-0000-000000000000 mtime 28670 num 0 gblnum 0 gblgen 0 gblbrk 0] Addr , gen 3,

links 1, type reg, flags 0, uid 0, gid 0, mode 600 len 520, nb 0 tbz 0, cow 0, newSinceEpoch 0,

zla 4305, bs 8192

tbz 0 means it is eagerzeroedthick.

PowerCLI shows that the disk is lazy zeroed :

C:\scripts> (Get-VM -name VMNAME).HardDisks[0].storageFormat

Thick

The question is which information is correct?

[a_p_]

Unless I'm mistaken, the tbz value is supposed to show the number of blocks not being zeroed yet. However, this value will also be zero in case of a newly create thin provisioned virtual disk. Are you sure the vmkfstools -D output is from the correct .vmdk file? To me it looks like this is a thin provisioned virtual disk on either a VMFS3 datastore with an 8MB block size, or an upgraded VMFS5 datastore.

André