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

Extension of a Clustered (shared) VMDK (67098)

Last Updated: 11/4/2020Categories: How toTotal Views: 34780Language:
English

22 like this article

Subscribe to get an email
newsletter with new updates

22 people found this helpful Please provide article feedback:

Purpose

After configuring a clustered VMDK a user needs to extend the size of the clustered (shared) disk.

Note: One of the common examples of using a clustered VMDK is Windows Server Failover Cluster (WSFC) with a disk resource shared across multiple VMs (starting with vSphere 7.x)

Impact / Risks

Online extension of a clustered disk is not supported

Note: Make sure to check this KB article regularly to get an update on the online extension procedure once available.

Offline extension of a clustered (shared) VMDK is supported but require reloading configuration files (*.vmx) for all VMs having an access to the disk(s) that has been extended You can reload the configuration files by:

Using the vMotion operation for all VMs having an access to the clustered disk. Select to change host only while executing the vMotion Wizard. Validated for WSFC.

Using command line options outlined in Reloading a vmx file without removing the virtual machine from inventory .

Removing and re-adding VMs with an access to the extended clustered disk from the vCenter Inventory. Note that operations generates a new VM Inventory ID (vmid), which might have an impact on the automation and operation of the VM. VMware does not recommend using this option.

Note: After extending a clustered VMDK from vSphere, make sure to follow the guest OS specific procedure and recommendations to extend the size of the disk in the Guest OS.

As with any VMDK manipulation, a working backup MUST be confirmed before any work is started.

Resolution

To extend a clustered VMDK, follow the steps below:

Obtain the path to the clustered VMDK to be extended (for example, /vmfs/volumes/shareddatastore/SQL01.vmdk)

Shut down all VMs, having access to the clustered VMDK to be extended.

Login to an ESXi host (SSH) with an access to the datastore where the clustered VMDK is stored.

Expand a clustered VMDK with the following command:

vmkfstools  -X|--extendvirtualdisk newSize[bBsSkKmMgGtT]

Specify the newSize parameter adding an appropriate unit suffix. The unit type is not case-sensitive. vmkfstools interprets either k or K to mean kilobytes. If you do not specify the unit type, vmkfstools defaults to kilobytes. The newSize parameter defines the entire new size, not just the increment you add to the disk.

Example: vmkfstools --extendvirtualdisk 2048G /vmfs/volumes/shareddatastore/SQL1.vmdk -d eagerzeroedthick

Note: As zeros are being written this will take a while.

Refresh the configuration file of VMs with the access to the extended clustered disks. VMware recommends using the vMotion operation or solutions listed in the Impact section of this KB article

Verify that the new disk size is correctly reflected on all VMs using "Edit Settings" section in the UI. If there are any discrepancies, remove the VMDK from that VM and readd it (“Add an existing disk”), making sure to use the same SCSI controller and ID.

Boot the first VM and grow the Guest filesystem. Use the Guest OS respective guidelines

Boot remaining VMs and confirm the functionality of the cluster.

Note: if you extend the clustered VMDK by using vSphere UI, you have no control over all the options to extend the disk. As a result, the EagerZeroedThick VMDK automatically becomes LazyZeroedThick. You would need to convert the disk to be EZT using the vmkfstools. For more details, see Attempts to extend the size of an EagerZeroedThick VMDK from the vSphere Client might result in a LazyZeroedThick VMDK

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)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vSphere ESXi 5.5

Take Our Survey

Support Assistant