Search the VMware Knowledge Base (KB)
View by Article ID

Delete All snapshot operation results in a Consolidate Helper snapshot when a datastore has insufficient disk space (1003302)

  • 45 Ratings

Details

If you try to initiate a Delete All snapshot for a virtual machine using Snapshot Manager, and if that virtual machine is on a datastore that does not have sufficient space for the snapshot, the following message displays in VMware Infrastructure (VI) Client:  
 
msg.hbacommon.outofspace: there is no more space for the redo log of <VMname>-0000xx.vmdk.

You are given the option to abort or retry.
  • If you choose Abort, the virtual machine is powered off, the snapshot is aborted, and a Consolidate Helper snapshot is created. The Snapshot Manager UI displays that Consolidate Helper snapshot. You can delete the Consolidate Helper snapshot after you have made space available.
  • If you click Retry, the Snapshot Manager returns to Consolidate Helper snapshot mode unless you have made more disk space available.

Solution

To resolve this issue, free up disk space if possible, or extend the VMFS volume using VI Client.
 
To extend the VMFS volume:
  1. Select the host on which the virtual machine resides and click the Configuration tab.
  2. Select the datastore on which the virtual machine resides and click Properties.

    Note: If there is no available storage, a new LUN must be presented to every ESX host that can see the LUN.

  3. In the dialog that appears, click Add Extent and follow the prompts in the Add Extend wizard to add an extent. 
  4. Perform a rescan on every ESX host that is being presented the new LUN so that the addition of the extent is detected.
  5. After you have extended the VMFS volume, you can check the Retry option of the Redo log pop-up. 
Caution: When using Delete All in the Snapshot Manager, the snapshot furthest from the base disk is committed to its parent, causing that parent snapshot to grow. When that commit is complete, that snapshot is removed and the process starts over on the newly updated snapshot to its parent. This continues until every snapshot has been committed. This can lead to an aggressive use of additional disk space if the snapshots are large. Use care when exercising this option if there is not much space available on the datastore.
 
If the snapshot manager does not display any snapshots, see Committing snapshots when there are no snapshot entries in the snapshot manager (1002310).
 
If you have run out of space and cannot delete all snapshots, clone the virtual machine to a different datastore (you can select a different destination for each virtual disk in the clone wizard). All of the snapshots are committed to the clone virtual machine.
 
If you have vCenter Server 4.x, you can prevent this issue by performing the steps in Configuring VMware vCenter Server to send alarms when virtual machines are running from snapshots (1018029).
 

Update History

05/07/2010 - Added link to KB 1002310 and 1018029. 07/05/2010 - Added links to the patch releases for ESX/ESXi 3.5 and 4.0. 09/18/2012 - Added ESX/ESXi 4.x to Products

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 45 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 45 Ratings
Actions
KB: