Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
You are unable to commit the snapshots even if the virtual machine is off The CID chain is not broken and there are no files missing You may see these messages in the /var/log/vmkernel.log file:Apr 26 20:43:12 esesx1 vmkernel: 41:00:03:12.522 cpu6:1040)Cow: 4464: Setting freeSector to 84991. bad root entries = 0, bad leaf entry = 0Apr 26 20:43:17 esesx1 vmkernel: 41:00:03:17.253 cpu6:1040)DevFS: 2222: Unable to find device: 4a750-ESFILE-000003-delta.vmdkApr 26 20:43:17 esesx1 vmkernel: 41:00:03:17.253 cpu0:1024)VMNIX: VMKFS: 1129: ESFILE-000003-delta.vmdk (304976), status -9Apr 26 20:43:17 esesx1 vmkernel: 41:00:03:17.253 cpu0:1024)VMNIX: VMKFS: 1129: ESFILE-flat.vmdk (313167), status -9Apr 26 20:43:56 esesx1 vmkernel: 41:00:03:56.275 cpu7:1040)Config: 416: "HostLocalSwapDirEnabled" = 1, Old Value: 1, (Status:0x0)Apr 26 20:45:15 esesx1 vmkernel: 41:00:05:15.434 cpu1:1040)DevFS: 2222: Unable to find device: 24752-ESFILE-000002-delta.vmdkApr 26 20:45:15 esesx1 vmkernel: 41:00:05:15.435 cpu0:1024)VMNIX: VMKFS: 1129: ESFILE-000002-delta.vmdk (149330), status -9Apr 26 20:45:15 esesx1 vmkernel: 41:00:05:15.435 cpu0:1024)VMNIX: VMKFS: 1129: ESFILE-flat.vmdk (182097), status -9Apr 26 20:46:10 esesx1 vmkernel: 41:00:06:10.651 cpu2:1138)World: vm 2539: 900: Starting world vmm0:ESMAP2 with flags 8Apr 26 20:46:10 esesx1 vmkernel: 41:00:06:10.651 cpu2:1138)Sched: vm 2539: 5333: adding 'vmm0:ESMAP2': group 'host/user': cpu: shares=-3 min=0 minLimit=-1 max=-1 You may see these messages in the /var/log/vmware/hostd.log file:[2009-04-26 21:23:34.521 'BaseLibs' 93047728 info] SNAPSHOT: Consolidating from '/vmfs/volumes/499b10c0-cc7aeb7a-0665-001a4bfe2edf/ESFILE/ESFILE_1-000013.vmdk' to '/vmfs/volumes/49703b96-89d28c54-4f8d-001a4bfe6fc5/ESFILE/ESFILE_1.vmdk'.[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] DISKLIB-VMFS : "/vmfs/volumes/49703b96-89d28c54-4f8d-001a4bfe6fc5/ESFILE/ESFILE_1-flat.vmdk" : failed to open (1048585): AIOMgr_Open failed. Type 3[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] DISKLIB-LINK : "/vmfs/volumes/49703b96-89d28c54-4f8d-001a4bfe6fc5/ESFILE/ESFILE_1.vmdk" : failed to open (Device or resource busy).[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] DISKLIB-CHAIN : "/vmfs/volumes/49703b96-89d28c54-4f8d-001a4bfe6fc5/ESFILE/ESFILE_1.vmdk" : failed to open (Device or resource busy).[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] DISKLIB-LIB : Failed to open '/vmfs/volumes/49703b96-89d28c54-4f8d-001a4bfe6fc5/ESFILE/ESFILE_1.vmdk' with flags 0x18 (Device or resource busy).[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] SNAPSHOT: SnapshotCombineDisks failed: 5[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] SNAPSHOT: SnapshotConsolidate failed 5[2009-04-26 21:23:34.528 'BaseLibs' 93047728 info] SNAPSHOT: Consolidate failed 5[2009-04-26 21:23:34.529 'BaseLibs' 93047728 info] Foundry operation failed with system error: Device or resource busy (16), translated to 5[2009-04-26 21:23:34.575 'vm:/vmfs/volumes/499b10c0-cc7aeb7a-0665-001a4bfe2edf/ESFILE/ESFILE.vmx' 19753904 warning] Failed toconsolidate disks after removing all snapshots: This function cannot be performed because the handle is executing another function If you power on the virtual machine, you receive the message indicating that the .vmdk file is busy The virtual machine does not power on Cloning the virtual disks of the virtual machine fails with this error:DISKLIB-DSCPTR: Failed to open extents for descriptor file in normal mode There are no VMkernel related processes running on the virtual machine. You can determine this by running the command:# grep -i VMNAME /proc/vmware/vm/*/names There are no pending tasks for the virtual machines on the ESX host. To check for pending tasks: Connect to the ESX host using the vSphere Client. Choose the virtual machine, click the Tasks and Events tab. You may see these processes in the Service Console for the virtual machine:# ps auxwww | grep -i VMNAMEroot 10539 1.6 0.1 2912 1188 pts/0 S Apr23 73:20 /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/63869377-d35e-4f08-90e0-da9982570f67.bin -r /dev/stdout /vmfs/volumes/R5DATA2/ESFILE/ESFILE_1-flat.vmdk /vmfs/volumes/R5DATA2/ESFILE/.ESFILE_1.vmdk.97cb6ac98a1d4558b9590548a96248d7.new.sigroot 10540 1.0 0.1 2788 1188 pts/0 S Apr23 45:30 /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/939bf818-d213-4817-adae-64fe0911f521.bin /vmfs/volumes/R5DATA2/ESFILE/.ESFILE_1.vmdk.97cb6ac98a1d4558b9590548a96248d7.last.sig /dev/stdin /dev/stdoutroot 10542 0.1 0.2 3704 1812 pts/0 S Apr23 6:10 ssh -o StrictHostKeyChecking no -p 22 -lroot esesxdr1.es.inet cat | /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/be02b66b-dca4-4a38-a352-aca0f78b049e.bin -c -d | /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/1d12a227-2374-4575-acdb-700d051c9fc9.bin --notruncate --status /dev/null --buffersizeMB 8 /dev/stdin /dev/stdout | /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/6839b7cd-e916-4ff2-976a-ec9a9f3d5af4.bin /dev/stdin /tmp/5f11fff2-e66b-4571-8ee2-45da738c8eb9 /dev/stdout | /tmp/.vzbin/da86968d-a5ef-4b66-b875-dbbee72ae8ad/02c99853-40d3-4a60-89d8-7c7caeb75185.bin /vmfs/volumes/VMFS1/ESFILE/ESFILE_1-flat.vmdk /dev/stdin /vmfs/volumes/VMFS1/ESFILE/.ESFILE_1.vmdk.97cb6ac98a1d4558b9590548a96248d7.new.sig /vmfs/volumes/VMFS1/ESFILE/.ESFILE_1.vmdk.97cb6ac98a1d4558b9590548a96248d7.delta
This issue may occur if the processes related to your backup utility from the original snapshot remains on the system. To resolve this issue stop the processes from the backup utility: Stop the backup service on the backup server and restart the backup server if necessary. From the service console, verify that there are no backup processes running. For more information, see Powering off an unresponsive virtual machine on an ESX host (1004340) or Powering off a virtual machine on an ESXi host (1014165). Commit a new snapshot. For more infromation, see the Basic System Administration guide. Note: If the snapshots were created by VMware Consolidated Backup and if no backup operations are in progress, run this command from the VMware Consolidated Backup proxy to stop all services: C:\Program Files\VMware\VMware Consolidated Backup Framework\vcbCleanup.bat
For related information, see: Understanding virtual machine snapshots in VMware ESX (1015180) Location of log files for VMware products (1021806)別のタスクが進行中であるため、仮想マシンのスナップショットをコミットできない无法提交虚拟机快照，因为正在进行其他任务