Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Virtual machine disk provisioning type changes unexpectedly (68107)

Last Updated: 11/12/2021Categories: InformationalTotal Views: 18998Language:
English

5 like this article

Subscribe to get an email
newsletter with new updates

5 people found this helpful Please provide article feedback:

Symptoms

After creating, migrating or cloning a virtual disk, you notice the provisioning type of the disk does not match what you selected in the UI or specified in the API call.

After a VM has been running for a period of time, you notice the provisioning type of a disk attached to that VM has changed from thin or thick to eager zeroed thick.

After snapshotting, restoring, or backing up a VM, you notice the provisioning type of a disk attached to that VM has changed.

After inflating, growing, shrinking, encrypting, or otherwise modifying a virtual disk, you notice its provisioning type has changed.

Note: The current provisioning type of a disk can be seen in the "Edit Settings" tab or the "VM Hardware" tile in the HTML5 UI.

Purpose

This article clarifies when virtual disk provisioning type can change on ESX hosts. (Disk provisioning type is sometimes called disk allocation type.)

Note: Virtual disk provisioning types are "thin", "thick" or "lazy zeroed thick" (LZT), and "eager zeroed thick" (EZT).
For more details, refer: Virtual Disk Provisioning Policies

Cause

In general, virtual disk provisioning type is a mutable property. It can change without warning and without manual intervention. There is no guarantee it will stay constant.

Such unexpected changes are especially common when NFS datastores are involved.

Disk provisioning type should be seen as a creation hint. VMware software will make a best-effort attempt to create and preserve a disk as the requested type but this sometimes isn't possible.

The only exception is for shared (multiwriter) disks on a VMFS datastore that are of eager zeroed thick (EZT) provisioning type. A shared disk on VMFS requires EZT provisioning, so VMware guarantees it will stay EZT as long as it stays on a VMFS datastore.

Resolution

This is an expected behavior.

It is not a bug and an issue should not be filed unless a specific VM operation fails with an error code because a virtual disk provisioning type has changed.

The only known situation where a change in provisioning type can cause a failure is discussed above:

A shared disk on a VMFS datastore must remain Eager Zeroed Thick or it will fail to open.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
无法在 HTML5 中使用外部网络查看或创建新网络连接 (67287)

KB
•
Workspace ONE Intelligent Hub 20.05 for iOS での動作変更 (80309)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere 7.0.x

Take Our Survey

Support Assistant