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

Products and Accounts

Support

Knowledge

Communities

Success

Learning

My Subscriptions

Loading

Knowledge Base

No more space for the redo log error when attempting to start a virtual machine (1002103)

Last Updated: 9/5/2010Categories: Total Views: 39309Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

When starting a virtual machine, a dialog appears stating there is no more space for the redo log , and prompts you to retry or abort.

Solution

The datastore in which the virtual machine resides in is out of disk space. The following are steps used to commit all snapshots and attain additional disk space.

Note: There may be corruption on the last snapshot if the virtual machine was abruptly powered down due to lack of disk space.

Identify any virtual machine with snapshots by running the following command at the service console:

Log into the console of the ESX host as root.

Run the following command:

find /vmfs/volumes -name *-0000[0-9][0-9]*.vmdk

Make note of all the file locations and the virtual machine names which include delta VMDK files.

All snapshots must be successfully committed to free up any disk space within the datastore. The snapshot commit process can be done in one of several ways.

Commit via the Virtual Infrastructure Client

Right-click on the identified virtual machine.

Click Snapshot > Snapshot Manager.

Click Delete All to commit all of the snapshots to the parent disk.

Commit via the Command Line

Log into the Service Console of the ESX host hosting the identified virtual machine as root.

Run the following command to list the virtual machines being hosted by this ESX host:

vmware-cmd -l

Run the following command to commit all snapshots of the virtual machine:

vmware-cmd <full path to vmx> removesnapshots

Note: There is no way to predetermine how long the commit process takes. If the size of the snapshot files are large, the commit process may exceed the default timeout of the VI Client, and a timeout message may be reported. Despite this timeout message, the commit process continues with no progress bar or status indicator. There is no way to predetermine the amount of time it takes to commit the snapshot as it depends too many factors which include, but are not limited to, snapshot size, array performance, HBA performance, fiber/network performance, and load.

In the event that space is an issue, there are certain operations which can be conducted to free up space for the purposes of committing the snapshots. The operations include:

Powering off the virtual machine

This operation deallocates the swap file. A virtual machine's swap file is usually the same size as the allocated amount of RAM. This operation does not have to be done to the machine which is running off of the snapshot. If the issue is affecting a production virtual machine, non-production machines residing in the same datastore can be powered off to free up storage for the commit operation. For more information, see http://www.vmware.com/pdf/esx3_memory.pdf .

Add an extent to the existing datastore

If there is a lack of disk space, the Add Extent wizard can be used to increase the amount of space available to this datastore. The Add Extent operation is irreversible, and creates a dependence of multiple LUNs for a single datastore. For more information, see http://www.vmware.com/pdf/vmfs-best-practices-wp.pdf .

Clone the virtual machine to a datastore that has more space

To clone the virtual machine to a datastore that has more space:

Right-click on the virtual machine which had been identified.

Select Clone.

Go through the clone wizard and select a datastore with adequate space.

Verify that the clone has no snapshots.

Start up the clone of the original virtual machine and verify that it is functioning in the same capacity as the original virtual machine.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware ESX Server

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.0.x

VMware ESX 4.1.x

VMware ESX 4.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