VMware Cloud Community
paquay_eric
Contributor
Contributor
‎09-01-2009 12:35 AM

Help needed : "Parent virtual disk has been modified since the child was created"

Hi all !

Yesterday, I've removed through the Virtual Infrastructue Client/Snaphost Manager, the snaphost who was existing on one of my VM.

Task did not produced any error message, then I've done a vMotion of this machine. Until that, nothing to complain.

Later, we've noticed that the machine was powered off. When I've tried to start it, I've received the message ""Parent virtual disk has been modified since the child was created".

From the snapshot manager, there's no snapshot, but if I am looking at the files into the datastores, they are still delta files.

Any help to fix this blocking situation will be helpful !

Eric

---

-rw------- 1 root root 704669696 Sep 1 09:13 s-dev-vtap-01-000001-delta.vmdk

-rw------- 1 root root 261 Sep 1 09:42 s-dev-vtap-01-000001.vmdk

-rw------- 1 root root 20350826496 Sep 1 09:39 s-dev-vtap-01-000002-delta.vmdk

-rw------- 1 root root 261 Sep 1 09:42 s-dev-vtap-01-000002.vmdk

-rw-rr 1 root root 37 Sep 1 09:24 s-dev-vtap-01-fe44739d.hlog

-rw------- 1 root root 12884901888 Sep 1 09:31 s-dev-vtap-01-flat.vmdk

-rw------- 1 root root 8684 Sep 1 09:31 s-dev-vtap-01.nvram

-rw------- 1 root root 406 Sep 1 09:31 s-dev-vtap-01.vmdk

-rw------- 1 root root 521 Sep 1 09:42 s-dev-vtap-01.vmsd

-rwxr-xr-x 1 root root 2989 Sep 1 10:03 s-dev-vtap-01.vmx

-rw------- 1 root root 268 Sep 1 09:39 s-dev-vtap-01.vmxf

-rw-rr 1 root root 1843748 Sep 1 09:31 vmware-16.log

-rw-rr 1 root root 31688 Sep 1 09:31 vmware-17.log

-rw-rr 1 root root 31404 Sep 1 09:31 vmware-18.log

-rw-rr 1 root root 32317 Sep 1 09:40 vmware-19.log

-rw-rr 1 root root 31322 Sep 1 09:42 vmware-20.log

-rw-rr 1 root root 31322 Sep 1 09:43 vmware-21.log

-rw-rr 1 root root 31322 Sep 1 10:03 vmware.log

---

file : s-dev-vtap-01-000001.vmdk

  1. Disk DescriptorFile

version=1

CID=54a389d4

parentCID=8558d85a

createType="vmfsSparse"

parentFileNameHint="s-dev-vtap-01.vmdk"

  1. Extent description

RW 25165824 VMFSSPARSE "s-dev-vtap-01-000001-delta.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7302"

---

file : s-dev-vtap-01-000002.vmdk

  1. Disk DescriptorFile

version=1

CID=08cc9bde

parentCID=30b51f76

createType="vmfsSparse"

parentFileNameHint="s-dev-vtap-01.vmdk"

  1. Extent description

RW 62914560 VMFSSPARSE "s-dev-vtap-01-000002-delta.vmdk"

  1. The Disk Data Base

#DDB

ddb.toolsVersion = "7302"

---

file : s-dev-vtap-01.vmdk

  1. Disk DescriptorFile

version=1

CID=8558d85a

parentCID=ffffffff

createType="vmfs"

  1. Extent description

RW 25165824 VMFS "s-dev-vtap-01-flat.vmdk"

  1. The Disk Data Base

#DDB

ddb.adapterType = "lsilogic"

ddb.geometry.sectors = "63"

ddb.geometry.heads = "255"

ddb.geometry.cylinders = "1566"

ddb.uuid = "60 00 C2 9d 90 b3 b9 ea-d8 4a fc 1f 1d 57 dc 04"

ddb.virtualHWVersion = "4"

ddb.toolsVersion = "7302"

---

file : s-dev-vtap-01.vmx

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

floppy0.present = "true"

nvram = "s-dev-vtap-01.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "manual"

powerType.powerOff = "default"

powerType.powerOn = "default"

powerType.suspend = "default"

powerType.reset = "default"

displayName = "s-dev-vtap-01"

extendedConfigFile = "s-dev-vtap-01.vmxf"

scsi0.present = "true"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "2048"

scsi0:0.present = "true"

scsi0:0.fileName = "s-dev-vtap-01-000001.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

sched.scsi0:0.shares = "normal"

ide0:0.present = "true"

ide0:0.clientDevice = "true"

ide0:0.fileName = ""

ide0:0.deviceType = "atapi-cdrom"

ide0:0.startConnected = "false"

floppy0.startConnected = "false"

floppy0.fileName = "/dev/fd0"

floppy0.clientDevice = "true"

ethernet0.present = "true"

ethernet0.allowGuestConnectionControl = "false"

ethernet0.networkName = "Agency Network"

ethernet0.addressType = "vpx"

ethernet0.generatedAddress = "00:50:56:8b:44:92"

guestOS = "winnetstandard"

uuid.bios = "50 0b f2 aa 3e 59 61 24-fb 9e 64 35 07 d8 ad 08"

log.fileName = "vmware.log"

snapshot.action = "keep"

sched.cpu.min = "0"

sched.cpu.units = "mhz"

sched.cpu.shares = "normal"

sched.mem.minsize = "0"

sched.mem.shares = "normal"

toolScripts.afterPowerOn = "true"

toolScripts.afterResume = "true"

toolScripts.beforeSuspend = "true"

toolScripts.beforePowerOff = "true"

scsi0:0.redo = ""

vmware.tools.requiredversion = "7302"

scsi0:1.present = "true"

scsi0:1.fileName = "s-dev-vtap-01-000002.vmdk"

scsi0:1.deviceType = "scsi-hardDisk"

ethernet0.startConnected = "true"

scsi0:1.redo = ""

tools.syncTime = "true"

uuid.location = "56 4d 5c 93 63 2c c1 30-8a 0a d0 6d 4a 28 22 d4"

sched.mem.max = "2048"

sched.swap.derivedName = "/vmfs/volumes/4624c57e-8ff9c610-4c4b-0018fe830594/s-dev-vtap-0

v-vtap-01-fe44739d.vswp"

migrate.hostlog = "./s-dev-vtap-01-fe44739d.hlog"

cpuid.1.ecx = "R--RR0

H-R"

cpuid.1.ecx.amd = "R--

R-"

cpuid.80000001.ecx.amd = "--

RR-RR--

"

cpuid.80000001.edx = "--R--

"

cpuid.80000001.edx.amd = "----

"

hostCPUID.0 = "00000006756e65476c65746e49656e69"

guestCPUID.0 = "00000006756e65476c65746e49656e69"

userCPUID.0 = "00000006756e65476c65746e49656e69"

hostCPUID.1 = "00000f68000408000000e5bdbfebfbff"

guestCPUID.1 = "00000f6800010800000020110febbbff"

userCPUID.1 = "00000f68000408000000e5bdbfebfbff"

hostCPUID.80000001 = "00000000000000000000000120000000"

guestCPUID.80000001 = "00000000000000000000000120000000"

userCPUID.80000001 = "00000000000000000000000120000000"

evcCompatibilityMode = "FALSE"

annotation = "WEB TEST: Olli MANTYRANTA: 05/01/2009 (FN)"

workingDir = "."

guest.commands.allowSharedSecretLogin = ""

guest.commands.sharedSecretLogin.com.vmware.vcIntegrity = ""

---

Eric

0 Kudos
1 Reply
vmw-sfraser
Enthusiast
Enthusiast
‎09-02-2009 08:24 AM

Hi paquay_eric

Unfortunately, this can happen when there is something wrong in the snapshot chain.

Please take a look at the following knowledge base article on troubleshooting snapshots.

Consolidating snapshots

http://kb.vmware.com/kb/1007849

I would strongly advise you to clone the VM out, as when you are in this situation there is no way to tell what happened to cause the original failure, and it's possible the VM data may be affected as well.

Cheers!






There are 10 types of people in this world. Those who understand binary, and those who do not.

There are 10 types of people in this world. Those who understand binary, and those who do not.
0 Kudos