Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides

Search the VMware Knowledge Base (KB)

View by Article ID

Troubleshooting an out of storage space condition in VMware vCenter Lab Manager

Symptoms

Files are not cleaned up automatically from the datastore
You run out of storage space
A context is not viewable
You see this error:

Virtual Machine Message - msg.hbacommon.corruptredo:The RedoLog of <virtual-disk-name>.vmdk has been detected to be corrupt. The virtual machine needs to be powered on. If the problem still persist, you need to discard the redolog.

Resolution

Warning: If virtual machines are running on a datastore and the disk becomes full it is possible that running virtual machines can become corrupted. Regularly check the amount of free space on your datastores to ensure that they are not about to run out of space. For more information, see Investigating disk space on an ESX host (1003564), or view the free space using the Virtual Infrastructure (VI) client, click Configuration > Storage. To understand disk space usage, see Assessing Virtual Machine Disk Space in the Lab Manager 2.x User Guide and View Virtual Machine Datastore Usage in the Lab Manager 3.x and 4.x User Guide.

Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Ensure that the virtual machine data storage is connected and working properly. For more information, see Identifying shared storage issues with ESX 3.x (1003659).
Check that the resource expiration settings are correct and garbage collection is working. For more information, see Setting the resource expiry and testing garbage cleanup functions in VMware vCenter Lab Manager (1006732).
Assess the storage directory tree and ensure that the correct set of virtual disk files (VMDKs) are present. For more information, see Viewing Virtual Machine Storage Usage.
Ensure that all ESX hosts being managed by Lab Manager are connected to the same datastores so that every template and virtual machine is accessible to each ESX host. For more information, see Verifying that ESX virtual machine storage is accessible (1003751).

Note:If your problem still exists after trying the steps in this article:

Gather the VMware Support Script Data. For more information, see Collecting diagnostic information for VMware Products (1008524).
File a support request with VMware Support and note this KB Article ID in the problem description. For more information, see How to Submit a Support Request.

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

1 2 3 4 5

1 2 3 4 5

Actions

Bookmark Document

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)