VM w/ strange vmdk layout


My apologies on such a newbie question BUT I was wondering if I could get some more eyes and input on this VM's disk layout. The E:\ drive (second hard disk file) will need to be expanded soon and when looking at the VM configuration I’m a bit puzzled...

Here we have it:

-rw------- 1 root root 3925868544 Sep 15 10:43 TAC-APP024-000001-delta.vmdk

-rw------- 1 root root 316 Sep 13 11:06 TAC-APP024-000001.vmdk

-rw------- 1 root root 7381975040 Sep 15 13:30 TAC-APP024_2-000001-delta.vmdk

-rw------- 1 root root 321 Sep 13 11:06 TAC-APP024_2-000001.vmdk

-rw------- 1 root root 59055800320 Sep 6 07:49 TAC-APP024_2-flat.vmdk

-rw------- 1 root root 345 Sep 6 07:49 TAC-APP024_2.vmdk

-rw-rr 1 root root 37 Apr 12 12:52 TAC-APP024-93a6539e.hlog

-rw------- 1 root root 2147483648 Sep 11 17:45 TAC-APP024-93a6539e.vswp

-rw------- 1 root root 21474836480 Sep 6 07:41 TAC-APP024-flat.vmdk

-rw------- 1 root root 8664 Sep 11 17:45 TAC-APP024.nvram

-rw------- 1 root root 4300308393 Sep 4 16:33 TAC-APP024-Snapshot88.vmsn

-rw------- 1 root root 342 Sep 6 07:41 TAC-APP024.vmdk

-rw------- 1 root root 2409 Sep 6 07:49 TAC-APP024.vmsd

-rwx------ 1 root root 1960 Sep 15 07:19 TAC-APP024.vmx

-rw------- 1 root root 254 Sep 15 07:19 TAC-APP024.vmxf

-rw-rr 1 root root 249275 Apr 12 10:44 vmware-21.log

-rw-rr 1 root root 42059 Apr 12 12:52 vmware-22.log

-rw-rr 1 root root 293696 Apr 26 06:01 vmware-23.log

-rw-rr 1 root root 30839 Apr 26 07:27 vmware-24.log

-rw-rr 1 root root 789665 Jul 11 16:43 vmware-25.log

-rw-rr 1 root root 351673 Aug 23 06:35 vmware-26.log

-rw-rr 1 root root 208706 Sep 15 13:36 vmware.log

In VIC, it has Hard disk 2 , disk file, set to "TAC-APP024_2-000001.vmdk" but yet i see "TAC-APP024_2.vmdk" in the folder which appears to be the primary? Does the ""TAC-APP024_2-000001.vmdk" mean it currently reverted to a snapshot? When I go to expand the drive will I be hitting the "TAC-APP024_2.vmdk" or the"TAC-APP024_2-000001.vmdk”?

I'm a little worried because i believe the last time I've seen this and tried to expand the "_2-000001.vmdk" it crashed the VM...

I attached a couple pics from VIC.

Thanks for the input / assistance.

0 Kudos
2 Replies

It's definately running on a snapshot.

If this isn't showing using snapshot manager in VC and via the vmware-cmd hassnapshots option then you have hit a bug to be corrected in ESX4 so I've been told.

The way around this is to clone the disks and add them back to the VM or another one.


/* Style Definitions */

p.MsoNormal, li.MsoNormal, div.MsoNormal






font-family:"Times New Roman";

mso-fareast-font-family:"Times New Roman";}

@page Section1



To clone a disk use vmkfstools –i source destination

The source will be a snapshot disk file. Use the path from

the vmware-cmd –l command, just remove the .vmx and add in the disk file name.

The destination can be on the same path (Datastore) or

alternatively a different path

Current paths of disks etc can be obtained by running

vmware-cmd –l


Darn bugs!

Okay, So I'll have to clone the current attached 'snapshot' disks, add them to a new VM (new .vmx is optional) , then i could continue on with a disk expansion...

Will be a pain, but okay. Thanks very much for the reply!

0 Kudos