• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 803
  • Last Modified:

Vmware Virtual Guest Datastore Space

I have a gust that crashed due to it being out of space. The Gust points to a 1TB datastore that ran out of space. The guest will not come back up due to being out of space. Is there something I can do to delete files from the volume?
0
Darrell Kirby
Asked:
Darrell Kirby
  • 15
  • 11
  • 3
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Why did it run out of space?

Do you have any Snapshots active in Snapshot Manager?

If so how large and how long have you been running on the Snapshot?
0
 
Darrell KirbyAuthor Commented:
I have attached a screenshot of what my datastore looks like. I do not have a snapshot for this DS. Is anything in the DS able to be deleted? How would I get to the data on the VMDK to delete some files?
Virtual-Space.docx
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
where has the space gone?
0
Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
What version of VMware is this?
0
 
Darrell KirbyAuthor Commented:
It is VSphere 4.5. The space was consumed by data from the user. The OS was showing more space than Vmware was showing.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Looks like a snapshot to me!

Check in Snapshot Manager, if there is a snapshot?

You've not changed memory on the VM recently?
0
 
Darrell KirbyAuthor Commented:
I have not changed any memory. When I look at snapshot it asks me if I want to revert to current Snapshot.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Well this is the issue, you've created a Snapshot at some time in the past.

You've let the snapshot grow (this is very dangerous), as you've now found out, because you can run out of space on the datastore. The VM is currenty running on the snapshot.

You should only use snapshots, for 2 days (my recommendation), and then committ, delete ALL. Only use for patching, on Microsoft Patch Tuesday, to rollback just in case a patch goes wrong.

To delete the Snapshot, which will merge the current delta file, into the main VMDK could take many hours or days to committ, but you also need to have datastore space to complete this operation and you have none.

At present, you don't have enough datastore space to Delete the snapshot, you don't have enough space to start the VM.

You either need to add space to the existing datastore, or move the existing VM off the datastore to a new datastore with more space.

what else is using the datastore?

Is this VM using the entire datastore?
0
 
Darrell KirbyAuthor Commented:
Yes. This VM is using the entire Datastore.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Snapshot has been running since the 13 February 2011.

It could take many hours to delete this, and it may not delete.

What is the server, and what are the sizes of the disks in properties.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay, this is a very large VM, you will need to create a new datastore on new disks
(is this possible on the server you have?)


or

Do you have vCenter? (you could clone this disk to another datastore, this would  get you out of Snapshot hell, and then, later delete the old VM (current one, after making clone).

or

use VMware Converter to Convert and MIgrate the data. (this is the recommended VMware way of getting out of Snapshot hell).

0
 
Darrell KirbyAuthor Commented:
The Server is a File server. The disk size is 940GB (Thick)
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It says MKS datastore only, do you have others?
0
 
Darrell KirbyAuthor Commented:
Yes. I have other datastores. None that have enough space for this.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
yes, you've got the largest Snapshot I've ever seen!

3G and 115GB.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
what are the total sizes of the disks?

does it have two disks?

is it just one single 940GB disk?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
do you have any space, anywhere, that you could use temp?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Are you using a SAN for datastores?
0
 
Darrell KirbyAuthor Commented:
I am in the process of deleting all Snapshots.
0
 
Darrell KirbyAuthor Commented:
Yes. it is a SAN.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Deleteing the Snapshot could fail, if you've not got enough disk space.

or do you mean on other datastores, so you can move it?

Do you have no other resource, disks or LUNs you can create to offer more space?
0
 
coolsport00Commented:
An option you could do, if your snapshot 'deleting' doesn't work, and for an option in the future, if you have the resources is to install something on your local workstation like VMware Player, which is free. Also, install vCenter Converter Standalone (if you don't have vCenter Server with Converter). You can then attach an external piece of storage and create a datastore on it through VMware Player and do a conversion of the ESX/i VM to your external storage to 'merge' the snaps during the conversion. Or, if you do have enough storage on another datastore, conversion or cloning will remove the snaps, if Snapshot Manager doesn't work for ya.

Some handy-dandy snapshot KBs I recommend looking at when you're able:
Understanding Snapshots: http://kb.vmware.com/kb/1015180
Snapshot Best Practices: http://kb.vmware.com/kb/1025279

Regards,
~coolsport00
0
 
Darrell KirbyAuthor Commented:
Thank you for that information. The snapshot is at 99% and is taking some time which i am told is normal for large snapshots.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, it could take a while to delete (merge the snapshot into the main vmdk disk).

Just keep an eye on the space on the datastore.
0
 
coolsport00Commented:
Oh yeah...with the size snaps we're talking about here, don't expect them to be finished anytime soon. Just monitor things a while and let us know if you run into issues...

~coolsport00
0
 
Darrell KirbyAuthor Commented:
It took 4 hours to selete the snapshot! I wil turn this off for this machine. Thank you!
0
 
coolsport00Commented:
Actually didn't take as long as I thought it would :) Kudos to you for having patience...many EE posters that have snapshot/datastore 'free space' issues wanna rush the process.

Best of luck!

Regards,
~coolsport00
0
 
Darrell KirbyAuthor Commented:
The deletion of the snapshot freed some space in order to get the machine back online.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That's pretty quick! Try not to use and leave snapshots running in future!
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 15
  • 11
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now