I did the following and wondering why it still saus thin:
1. created a thin disk via gui
2. I ran vmkfstools -i file.vmdk -d zeroedthick file1.vmdk
3. Removed file.vmdk from vm
4. Added file1.vmdk to vm ( during adding the vmdk it said it was thick)
5. Now in edit settings the new drive says thin disk even though i know its thick.
Is this default, or a bug?
Thanks
William
I performed the exact process you mentioned in your post and did not experience the issue you stated. When I attached the new VMDK it reported as thick during the add. I clicked OK to the "edit settings" dialog which committed the VMDK add. I checked back in "edit settings" and it still reported as thick. I then proceeded to boot the test VM and check the setting again--still thick. I am running fully patched ESX and vCenter.
VCP 3, 4
I performed the exact process you mentioned in your post and did not experience the issue you stated. When I attached the new VMDK it reported as thick during the add. I clicked OK to the "edit settings" dialog which committed the VMDK add. I checked back in "edit settings" and it still reported as thick. I then proceeded to boot the test VM and check the setting again--still thick. I am running fully patched ESX and vCenter.
VCP 3, 4
I forgot to mention that this running on esxi 4 and using NFS off of Netapp.
Would that make a difference?
I think NFS VMDks are always thin regardless of the setting you use in the GUI.
VCP 3, 4
Hmm So a default setting (which I presume we cannot change) is all vmdks are considered thin over NFS? Even if they are considered thick?
Check out the NFS section in this VMware KB http://kb.vmware.com/kb/1005418
VCP 3, 4
Good KB but could not run du on esxi 4 u1
Thank you for your help.