posted

12 Comments

A performance issue has recently been discovered in the VAAI Thin Provisioning Block Reclaim mechanism introduced in vSphere 5.0. This feature allows an ESXi host to tell the array that a block on a Thin Provisioned datastore is no longer needed and can be reclaimed. This could be the result of a file delete operation, a Storage vMotion, a Snapshot Consolidate operation, etc. I blogged about the reclaim feature some time ago.

What we have found is that the time taken to complete the Block Reclaim operation could perform poorly.

Unfortunately, in light of this performance issue, VMware are advising that the UNMAP feature be disabled in ESXi 5.0 until further notice.

A KnowledgeBase article, 2007427, has now been published and contains an additional description of the issue and details on how to disable the UNMAP feature. Click here to read the KB.

Get notification of these blogs postings and more VMware Storage information by following me on Twitter: Twitter @VMwareStorage

About the Author

Cormac Hogan

Cormac Hogan is a Senior Staff Engineer in the Office of the CTO in the Storage and Availability Business Unit (SABU) at VMware. He has been with VMware since April 2005 and has previously held roles in VMware’s Technical Marketing and Technical Support organizations. He has written a number of storage related white papers and have given numerous presentations on storage best practices and vSphere storage features. He is also the co-author of the “Essential Virtual SAN” book published by VMware Press.