We are unable to resize the VM disk and seeing the following error when we try to do. Have tried to extend with VM poweroff and also consolidated the snapshots but no use. Let me know if you need more details.
[root@myesxhost:/vmfs/volumes/vvol:9306e2643eae41e5-8004f38b148bbbdd/rfc4122.dd87ee03-92d9-4f51-a1e3-5514a669e46e] vmkfstools -e mytestvm_1-000001.vmdk
Failed to open disk link /vmfs/volumes/vvol:9306e2643eae41e5-8004f38b148bbbdd/rfc4122.dd87ee03-92d9-4f51-a1e3-5514a669e46e/mytestvm_1-000001.vmdk :Failed to lock the file (16392)Disk chain is not consistent : Failed to lock the file (16392)
Does anyone know how to fix the file descriptor mismatch ? Is there an alternative solution or way way to fix like copy the vmdk to new disk ?
Any referrence KB's would be be helpful.
If it's only the snapshot chain which is inconsistent, it can easily be fixed, by setting the value for the parentCID to that of the parent .vmdk file's CID.
However, a CID mismatch usually occurs due to a modification of the parent file (e.g. mounting it to a VM without the snapshot). In such cases it likely that the guest file system will show some corruption after fixing the snapshot chain. So make sure to create another snapshot after fixing the chain, and before powering on the VM.
I tried earlier today by updated the snapshots parentCID to match the parent's vmdk CID , but that didn't help. Could you please tell me what should be updated ?
After updated it was showing as 0 size on the edit settings of the vm. Please let me know what did I miss here ?
Also when its powered off , if i run vmkfstools -e <snapshot.vmdk> it is showing as Disk chain is consistent , it throws error only when its on.
Here is the details of my VMDK files.
mytestvm_1-000001-ctk.vmdk ( this has parentCID=ffffffff and CID=abcd1234 ) --> I updated the parentCID to match CID of below vmdk
mytestvm_1-ctk.vmdk ( this has parentCID=ffffffff and CID=efgh1234 )
The "-ctk.vmdk" files are used to track changes to e.g. optimize backups.
What I'd suggest is that you shut down the VM, and then delete the "-ctk.vmdk" files.
The important .vmdk files are the small header/descriptor files (e.g. "vmname.vmdk"), and the ones which contain user data (flat, delta, and/or sesparse).
After deleting the ctk files you should be able to consolidate/delete the snapshots from the Snapshot Manager. If no snapshot shows up in the Snapshot manager, create a new one, and then click the "Delete All" button.
The ctk files will usually be recreated by the backup software.
I assume that the mentioned ".bck" file is a typo, and shoud read ".lck". That's a lock file which usually exists while the VM is powered on.
Ok. Deleting the -ctk.vmdk and consolidating snapshots should fix the issues ? Sorry about .bck file that was a backup file which I took before editing.
The error throws only for the snapshot disk. So no modification of parentCID needed and just consolidation should work ? Does the vm needs to be powered off and consolidate the snapshots ?
[root@myesxihost:/vmfs/volumes/vvol:9306e2643eae41e5-8004f38b148bbbdd] vmkfstools -e myguestvm_1.vmdk
Disk chain is consistent.
[root@myesxihost:/vmfs/volumes/vvol:9306e2643eae41e5-8004f38b148bbbdd] vmkfstools -e myguestvm_1-000001.vmdk
Failed to open disk link /vmfs/volumes/vvol:9306e2643eae41e5-8004f38b148bbbdd/rfc4122.dd87ee03-92d9-4f51-a1e3-5514a669e46e/ptl12orddb103_1-000001.vmdk :Failed to lock the file (16392)Disk chain is not consistent : Failed to lock the file (16392)