VMware Cloud Community
tharpy
Contributor
Contributor

VMFS filling up

I have a customer that is seeing his vmfs fill up with log and dump files (in the vm's directory on vmfs3). It appears that this goes on until the vm eventually will not start because of the lack of space on the vmfs.

a week ago, we cleared out almost 20G of files and moved some VM's to make space....this week, it happened again.

Guest is Windows 2003Standard VM running as a file server.

Just wondering if anyone's seen something like this before.

Reply
0 Kudos
3 Replies
grasshopper
Virtuoso
Virtuoso

please provide the relevant data from the offending vmware.log files.

Reply
0 Kudos
tharpy
Contributor
Contributor

actually, it wasn't the log files that are the problem...I just got a screenshot of their storage browser...they're running snapshots of their file server and have not been committing the snaps.

that'll do it.

thanks

Reply
0 Kudos
tharpy
Contributor
Contributor

Here's an update. Problem is caused by snapshots left running for several weeks. So, we go into the snapshot manager within VC for that VM and delete the snapshot. Bummer is, although the snapshot manager shows no snapshots left, the delta file does not go away (as it should) and it just keeps growing.... So now, I've got the original state vmdk and the delta.vmdk and the delta is still growing every day.

We ran a command line hassnap command and the esx host doesn't see that the vm has a snapshot.

Question...will ESX let us cold-clone a VM that has both vmdk and delta.vmdk files and if it does, will it copy both, leaving us in the same situation? Remember, ESX and VC don't see that there's a snapshot.

OR is it that we just didn't wait long enough for the delta to committ? Maybe we'll come to work tomorrow and see all back together? The file server has total disk approaching 500G.

Current environment: ESX 3.0.1 patched, Latest VC w/patches, IBM 3650 and IBM DS-4700 storage.

Any insight?

Message was edited by:

tharpy

Reply
0 Kudos