Loading

×Sorry to interrupt
CSS Error

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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Storage vMotion operation fails with the error: Insufficient disk space on datastore (1008171)

Last Updated: 3/21/2024Categories: TroubleshootingTotal Views: 47166Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

A Storage vMotion operation fails

The virtual machine is no longer running

When clicking on the Complete Migration option, you see the error:

Insufficient disk space on datastore 'Datastore_Name'.

The virtual machine configuration file (.vmx) contains entries similar to:

scsi0:0.present = "true"
scsi0:0.fileName = "/vmfs/volumes/49672631-2d78df3f-92f9-001e0bdbbd68/VMname//DMotion-scsi0:00_VMname.vmdk"
scsi0:1.present = "true"
scsi0:1.fileName = "/vmfs/volumes/49672631-2d78df3f-84b3-001e0bdbbd68/VMname//DMotion-scsi0:01_VMname_1.vmdk"
scsi0:0.DMotionParent = "/vmfs/volumes/49672631-2d78df3f-92f9-001e0bdbbd68/VMname/VMname.vmdk"
scsi0:1.DMotionParent = "/vmfs/volumes/49672631-2d78df3f-84b3-001e0bdbbd68/VMname/VMname_1.vmdk"

In the vmware.log file, you see entries similar to:

vcpu-2| [msg.hbacommon.outofspace] There is no more space for the redo log of /vmfs/volumes/4cbf9f23-03a508eb-df4a-0019bbead771/Stcexcpmb16_1//DMotion-scsi0:08_Stcexcpmb16_2.vmdk. You
vcpu-2| may be able to continue this session by freeing disk space on
vcpu-2| the relevant partition, and clicking Retry. Otherwise,
vcpu-2| click Abort to terminate this session.
vcpu-2| ----------------------------------------
vcpu-2| Msg_Question: msg.hbacommon.outofspace reply=0
mks| MKS REMOTE failed to complete async op for authd connection!
vcpu-2| Msg_Question:

Resolution

This issue occurs if the destination datastore does not have enough free space to accommodate the storage migration operation.

For the complete list of Storage vMotion requirements, see the section Storage vMotion Requirements and Limitations in the Basic System Administration guide.

To resolve this issue, you must ensure that you have an adequate amount of free space on the datastores. To free up space, consider:

Moving virtual machines or individual virtual disks to another Datastore to free space

Doing the Storage vMotion to different destinations, where each one has enough free space to allocate the migrated vDisks.

Removing old snapshots

Cleaning up VMware VMFS

Adding additional datastores

Increasing capacity

For more information about these operations, see Troubleshooting a datastore or VMFS volume that is full or near capacity (1003412).

You may have most of the options greyed out in the VMware Infrastructure (VI) Client. This occurs if the virtual machine is in the middle of a migration process. No changes are allowed until that migration task is completed. The Remove from Inventory and Add to Inventory options do not impact the status of the virtual machine.

To set the migration status of the virtual machine as completed:

Edit the .vmx file and comment out the Dmotion lines (using #). For more information, see Storage vMotion fails with a generic DMotion error (1009113).

Reload the virtual machine settings with the command:

In ESX:

# vmware-vim-cmd vmsvc/getallvms
# vmware-vim-cmd vmsvc/reload VMID_from_previous_command

In ESXi:

# vim-cmd vmsvc/getallvms
# vim-cmd vmsvc/reload VMID_from_previous_command

Note: Re-registering the virtual machine also has the same effect. For more information, see Registering or adding a virtual machine to the inventory (1006160) .

Retry the Storage vMotion operation after ensuring that the datastore has enough free space and that the migration status is completed.

Perform these operations to ensure a successful Storage vMotion:

Whenever possible, use an ESX/ESX 4.x host to perform the Storage vMotion process. The ESX host does not use snapshots for the task.

If the virtual machine is big, perform the Storage vMotion operation in multiple steps by moving one virtual disk at a time. To move one virtual disk at a time, start the Storage vMotion wizard, on the Select Datastore screen, click Advanced and move only one disk at a time.

Related Information

For related information, see vCenter Server 4.0 vMotion operation fails with the error: Insufficient disk space on datastore (1014176).

Storage vMotion fails with a generic DMotion error
Storage vMotion での操作に次のエラーで失敗する：データストアのディスク容量が不足しています

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 ESX Server

Related Versions:

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant