hello everyone I extended a disk format eager zeroed from 60 gb to 200 gb using the gui and I found that the disc format has become lazy zeroed both from commandline interface with the command vmkfstools-t0 and from the gui.
Now I read that I can convert a lazy zeroed disk to eager zeroed using the command vmkfstools-k
Is enough converting the disk in this way ?
I tried this on a test machine and even though the interface still see the disk format lazy zeroed but from the command line, using vmkfstools-t0 I see that no sector has the Z.
can someone help me?
Thank you,
Manuel
Hi Manuel,
Take a look the bottom of http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101117...
it mentions :
"
"
hope this helps
Hi John
In a test vm (after exetuting the command vmkfstools -k vitdbssql04prd1_1.vmdk)
/vmfs/volumes/4f58c82c-d4a8ea84-fe99-5cf3fce89c3e/vitdbssql04prd1 # vmkfstools -t0 vitdbssql04prd1_1.vmdk
Mapping for file vitdbssql04prd1_1.vmdk (21474836480 bytes in size):
[ 0: 21474836480] --> [VMFS -- LVID:50f52554-22979b7a-5861-5cf3fce89c3e/4f58c82b-ec3f58f8-2a7a-5cf3fce89c3e/1:( 148660813824 --> 170135650304)]
But from gui I see always lazy zeroed.
Then from the gui I removed this disk (only disassociated it from vm) and readded and also from the gui I see that disk is eager zeroed.
So I think the problem is solved.
But I think this is also a bug on esxi 5, it is possible ?
Thanks,
Manuel