Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 678
  • Last Modified:

VM Error

Message from ESX-01.domain.LOCAL: There is no
more space for virtual disk ts-01-000002.vmdk.
You may be able to continue this session by freeing
disk space on the relevant partition, and clicking
Retry. Otherwise, click Abort to terminate this
session.
info

I received the above message after a server became unresponsive. On checking the Datastore there was an additional 60Gb free space.

The VM its self has a single 50Gig drive
VM File list

just want confirmation of the two large files there

Thanks
 
0
ncomper
Asked:
ncomper
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You've got a Snapshot attached to the Virtual Machine, and it's been left to fill up the datastore.

Check the Virtual Machine Properties, Right Click the Virtual Machine and Select Snapshot, and check Snapshot Manager if you have a snapshot present.
0
 
coolsport00Commented:
If there isn't any space left on the datastore (and yes, it's because of the snapshot as mentioned above), you won't be able to remove the snap by going into Snap Mgr, or by using cmd line. You need some space to do the snap removal. A quick way to gain space on the datastore is to power down the VM. This will remove the .vswp (swap) file, which in your case would give you an instant 6GB available space on the datastore. If there are any other VMs you can power down, do so, just to gain the space so you can remove the snap. You may not need to power down other VMs if powering down this one allows you to remove the snap.

-Pwr down VM
-Rt-click on VM -> Snapshot -> Snapshot Manager
-Click 'Delete All' button

What the Delete does is "commit" all data in the snap to the parent disk of the snapshot file. Once all data is committed (written) to the parent, the snapshot file is then deleted. If there are more than 1 snapshots attached to a VM, this process continues up the "snapshot heirarchy" until all data is written and snapshot files are removed. It looks like from your screenshot that, in your case, you only have 1 snap. When you do delete the snap, you will notice in the tasks that it will seem hung at 95%. That is normal...it will stay there until all data is committed, then the snap will be deleted, and it will finish. Since your snap isn't too large, I suspect it to be done in around 15-30mins.

Here are a couple KBs to help learn more about snapshots:
Understanding - http://kb.vmware.com/kb/1015180
Best Practices - http://kb.vmware.com/kb/1025279

Regards,
~coolsport00
0
 
ncomperAuthor Commented:
Both answers were correct, just loved the extra detail in the 2nd for the additional points
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now