VMWare Virtual Disks creating 2 files
Hi all,
We are running VMWare Server 1.0.2 Build 39867 and have an interesting behaviour with one of the VM's it runs.
One of the VM's has 3 Virtual disks as below
C 17 gig
D 20 gig
E 20 gig
However in the directory on the host that stores those virtual disks I noticed it was using almost twice the space.
Files are NZLSVPRT003-C-flat.vmdk (17 Gig)
NZLSVPRT003-D-flat.vmdk (20 Gig)
NZLSVPRT003-E-flat.vmdk (20 Gig)
NZLSVPRT003-C.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-D.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-E.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-C-000001.vmdk (12 Gig)
NZLSVPRT003-D-000001.vmdk (19 gig)
NZLSVPRT003-E-000001.vmdk (20 gig)
The vmx file has the following.
scsi0:0.present = "TRUE"
scsi0:0.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:0.redo = ""
scsi0:1.present = "TRUE"
scsi0:1.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:1.redo = ""
scsi0:2.present = "TRUE"
scsi0:2.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:2.redo = ""
So considering that I would expect the VM to be firing up the monolithicsparse -000001 virtual disks and the others are not required.
However what I am seeing in the vmware log is different.
It definitely opens the -000001 files, however then it proceeds to open the -flat files and their descriptor files.
The upshot of which is the virtual disks are taking almost twice as much space as they should.
Please note, there is another VMWare VM running on the same host not exhibiting the problem. Anyone got any ideas why this is and how I resolve the issue?
Thanks in advance for any help.
We are running VMWare Server 1.0.2 Build 39867 and have an interesting behaviour with one of the VM's it runs.
One of the VM's has 3 Virtual disks as below
C 17 gig
D 20 gig
E 20 gig
However in the directory on the host that stores those virtual disks I noticed it was using almost twice the space.
Files are NZLSVPRT003-C-flat.vmdk (17 Gig)
NZLSVPRT003-D-flat.vmdk (20 Gig)
NZLSVPRT003-E-flat.vmdk (20 Gig)
NZLSVPRT003-C.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-D.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-E.vmdk (1k descriptor file referencing the -flat file)
NZLSVPRT003-C-000001.vmdk (12 Gig)
NZLSVPRT003-D-000001.vmdk (19 gig)
NZLSVPRT003-E-000001.vmdk (20 gig)
The vmx file has the following.
scsi0:0.present = "TRUE"
scsi0:0.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:0.redo = ""
scsi0:1.present = "TRUE"
scsi0:1.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:1.redo = ""
scsi0:2.present = "TRUE"
scsi0:2.fileName = "F:\NZLSVPRT003\NZLSVPRT00
scsi0:2.redo = ""
So considering that I would expect the VM to be firing up the monolithicsparse -000001 virtual disks and the others are not required.
However what I am seeing in the vmware log is different.
It definitely opens the -000001 files, however then it proceeds to open the -flat files and their descriptor files.
The upshot of which is the virtual disks are taking almost twice as much space as they should.
Please note, there is another VMWare VM running on the same host not exhibiting the problem. Anyone got any ideas why this is and how I resolve the issue?
Thanks in advance for any help.
Apr 20 12:28:16: vmx| DISK: OPEN scsi0:0 'F:\NZLSVPRT003\NZLSVPRT003-C-000001.vmdk' persistent R[(null)]
Apr 20 12:28:16: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-C-000001.vmdk" (0xa)
Apr 20 12:28:16: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-C-000001.vmdk' (0xa): monolithicSparse, 35651584 sectors / 17408 Mb.
Apr 20 12:28:16: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-C-flat.vmdk" 0 (0xe)
Apr 20 12:28:16: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-C.vmdk' (0xe): monolithicFlat, 35651584 sectors / 17408 Mb.
Apr 20 12:28:16: vmx| DISKLIB-LIB : Opened "F:\NZLSVPRT003\NZLSVPRT003-C-000001.vmdk" (flags 0xa).
Apr 20 12:28:16: vmx| DISK: OPEN 'F:\NZLSVPRT003\NZLSVPRT003-C-000001.vmdk' Geo (2219/255/63) BIOS Geo (2219/255/63) freeSpace=30279Mb
Apr 20 12:28:16: vmx| DISK: OPEN scsi0:1 'F:\NZLSVPRT003\NZLSVPRT003-D-000001.vmdk' persistent R[(null)]
Apr 20 12:28:17: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-D-000001.vmdk" (0xa)
Apr 20 12:28:17: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-D-000001.vmdk' (0xa): monolithicSparse, 41943040 sectors / 20480 Mb.
Apr 20 12:28:17: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-D-flat.vmdk" 0 (0xe)
Apr 20 12:28:17: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-D.vmdk' (0xe): monolithicFlat, 41943040 sectors / 20480 Mb.
Apr 20 12:28:17: vmx| DISKLIB-LIB : Opened "F:\NZLSVPRT003\NZLSVPRT003-D-000001.vmdk" (flags 0xa).
Apr 20 12:28:17: vmx| DISK: OPEN 'F:\NZLSVPRT003\NZLSVPRT003-D-000001.vmdk' Geo (2610/255/63) BIOS Geo (2610/255/63) freeSpace=30279Mb
Apr 20 12:28:17: vmx| DISK: OPEN scsi0:2 'F:\NZLSVPRT003\NZLSVPRT003-E-000001.vmdk' persistent R[(null)]
Apr 20 12:28:17: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-E-000001.vmdk" (0xa)
Apr 20 12:28:17: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-E-000001.vmdk' (0xa): monolithicSparse, 41943040 sectors / 20480 Mb.
Apr 20 12:28:17: vmx| DISKLIB-DSCPTR: Opened [0]: "NZLSVPRT003-E-flat.vmdk" 0 (0xe)
Apr 20 12:28:17: vmx| DISKLIB-LINK : Opened 'F:\NZLSVPRT003\NZLSVPRT003-E.vmdk' (0xe): monolithicFlat, 41943040 sectors / 20480 Mb.
Apr 20 12:28:17: vmx| DISKLIB-LIB : Opened "F:\NZLSVPRT003\NZLSVPRT003-E-000001.vmdk" (flags 0xa).
Apr 20 12:28:17: vmx| DISK: OPEN 'F:\NZLSVPRT003\NZLSVPRT003-E-000001.vmdk' Geo (2610/255/63) BIOS Geo (2610/255/63) freeSpace=30279MbSOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I'd powerdown the VM mcahine, backup up that folder containing the HDD and then remove the snapshot file and power it back on and you should be good. As you do say snapshots are disabled and the file shouldnt be in use.
ASKER
Nothing on VMware console indicates there is a previous snapshot.
None of the vmdk's are read only.
I'm not saying your incorrect, but why would VMWare tell me otherwise.
None of the vmdk's are read only.
I'm not saying your incorrect, but why would VMWare tell me otherwise.
ASKER
@alienvoice Unfortunately finding the space to take a cope could be interesting it itself. (Yes i know it's only 60 gig, I didn't spec this machine otherwise it would have had a lot more space).
This is why I'm looking at disk space and how to get some back.
This is why I'm looking at disk space and how to get some back.
ASKER
OK, another question assuming these are snapshot files.
Considering the date modified on the -000001 vmdk files are dated 4 days ago (last time it was rebooted I'd say), and the -flat files last modified date is in 2007, I'm assuming I would want to be deleting the -flat files and their descriptor files.
I would definitely not want to be going to back a system state of 2007.
I can understand why we all think these are a snapshot, It's just VMWare Server is disagreeing.
Cheers
Terry
Considering the date modified on the -000001 vmdk files are dated 4 days ago (last time it was rebooted I'd say), and the -flat files last modified date is in 2007, I'm assuming I would want to be deleting the -flat files and their descriptor files.
I would definitely not want to be going to back a system state of 2007.
I can understand why we all think these are a snapshot, It's just VMWare Server is disagreeing.
Cheers
Terry
Try to take a snapshot then wait a few minutes and then try and consolidate it by deleting the created snapshot.
Hopefully this will clear all your snaps.
Hopefully this will clear all your snaps.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, I'm getting a couple of 140 gig drives added to this server next week. That will allow me to shut the VM down and take a backup.
Will let you know how I get on.
Thanks,
Tel
Will let you know how I get on.
Thanks,
Tel
I would also recommend, updating to the latest and last version of VMware Server 2.0.2, which was discontinued in 2009, and extended support ended last year in June 2011.
ASKER
Still working on this waiting on the disks to be installed.
ASKER
Thank you all very much.
After reading up about rogue snapshots (as was the case for us) I decided to use vmware-vdiskmanager command line tool to merge the flat and snapshot files into 1 flat disk and then test those disks before removing the old ones.
Everything went as expected and the VM is now using the amount of diskpace it should.
Cheers,
Tel
After reading up about rogue snapshots (as was the case for us) I decided to use vmware-vdiskmanager command line tool to merge the flat and snapshot files into 1 flat disk and then test those disks before removing the old ones.
Everything went as expected and the VM is now using the amount of diskpace it should.
Cheers,
Tel
Good to hear.
ASKER
Thanks again, I only wish I could have doubled the points for this question.
ASKER
In VMWare Console it says Snapshots are disabled and also that there is No Current Snapshot.
(vmx file has snapshot.disabled = "TRUE" as it's last line)
Thanks,