The VMDK chain gets broken after using VixDiskLib_CheckRepair() for a file(other than the last child) in the VMDK chain.

Hi,

I'm opening a VMDK file in R/W mode and processing it.In mid of this the application gets crashed before closing the VMDK file.

If the application crashes before closing the VMDK file.,We will not be able to open the vmdk file again.

As Thomas suggested earlier (http://communities.vmware.com/thread/438208) ,I'm using the below method to Repair and reuse the VMDK file.

// Open disk to mount

     VixDiskLibHandle lnv_mountDiskHandle = NULL;

     li_vixError = VixDiskLib_Open(lnv_connection, MOUNT_DISK_NAME,

          MOUNT_RW ? 0 : VIXDISKLIB_FLAG_OPEN_READ_ONLY, &lnv_mountDiskHandle);

     if (VIX_ERROR_CODE(li_vixError) == VIX_E_DISK_NEEDSREPAIR)

     {

          li_vixError = VixDiskLib_CheckRepair(lnv_connection, MOUNT_DISK_NAME,

               TRUE);

          li_vixError = VixDiskLib_Open(lnv_connection, MOUNT_DISK_NAME,

               MOUNT_RW ? 0 : VIXDISKLIB_FLAG_OPEN_READ_ONLY

               , &lnv_mountDiskHandle);

     }

     ABORT_IF_ERROR(li_vixError)

The Repair method is changing the CID of the VMDK file in Descriptor file.

In my case I'm having the below VMDK chain

win2012-flat.vmdk

win2012-child1.vmdk

win2012-child2.vmdk

win2012-child3.vmdk

In the above chain if i will open and use the last file (win2012-child3.vmdk) and Repair it for using aging.

The VixDiskLib_CheckRepair() method is changing the CID of the file.But it will not affect anything in the above scenario because I'm opening the last file of the chain.

But if i will open the VMDK file other than the last file in the chain.,The VixDiskLib_CheckRepair() method is changing the CID of the file and it is affecting the chain.

Example:

If i will open the first child(win2012-child1.vmdk) and Repair it while opening it after the application crash.

The VixDiskLib_CheckRepair() method is changing the CID of the file(win2012-child1.vmdk).

In the chain the second child[win2012-child2.vmdk] (Immediate child of the opened file) is having the CID of the Parent VMDK file[parentCID=8d7a6a29]

But while repairing the first child it will change the CID of that file.,But the second child[win2012-child2.vmdk] having the older parentCID of the win2012-child1.vmdk file so the link gets broken.

If i will open the VMDK file(from Child 2) After the above scenario.,It throws the below error

"The parent virtual disk has been modified since the child was created.The content ID of the parent virtual disk does not match the corresponding parent content ID in the child."

How to solve this issue?

Any help on this is much appreciated.

Thanks

manickam