VMware Cloud Community
tkuo
Contributor
Contributor
Jump to solution

ESXi 5.0 U1 VAAI Behavior

Hi,

On ESX5.0u1 ( 623860),  by default vaai unmap is disabled:

# esxcli system settings advanced list -o /VMFS3/EnableBlockDelete | grep "Int Value"

Int Value: 0

Default Int Value: 0

Even after turning it on by issuing the following command

# esxcli system settings advanced set --int-value 1 --option /VMFS3/EnableBlockDelete

Array is not receiving any unmap calls . (What is the expected behaviour for esx5.0u1 ) ?

Unmap works from esx5.0 (469512).

Thanks in advance!

Reply
0 Kudos
1 Solution

Accepted Solutions
CHogan
VMware Employee
VMware Employee
Jump to solution

For better or for worse, this is by design. Please have a read of this blog post for further details.

http://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html

HTH

Cormac

http://cormachogan.com

View solution in original post

Reply
0 Kudos
2 Replies
CHogan
VMware Employee
VMware Employee
Jump to solution

For better or for worse, this is by design. Please have a read of this blog post for further details.

http://blogs.vmware.com/vsphere/2012/04/vaai-thin-provisioning-block-reclaimunmap-in-action.html

HTH

Cormac

http://cormachogan.com
Reply
0 Kudos
tkuo
Contributor
Contributor
Jump to solution

Thanks Cormac, appreciate the pointer to your blog post.  That really helped.

Tony

Reply
0 Kudos