Wednesday, July 10, 2013

Snapshot can not be deleted, snapshot issues

Error messages:

Remove snapshot servers01 The virtual disk is either corrupted or not a supported format.
Remove snapshot servers01 Unable to access file <unspecified filename> since it is locked

Suspected reason behind snapshot problem is VMFS3 Heap size

Referring to Knowledge base article from VMware

Log entries in ESXiS00004:

VMKernel Log entries:

vmkernel: 5 cpu9:0000000)World: vm 5281127: 1540: Starting world vmm1:server01 with flags 4008
vmkernel: cpu9:0000000)WARNING: Heap: 2218: Heap cow already at its maximumSize. Cannot expand.
vmkernel:  cpu9:00000000)WARNING: Heap: 2481: Heap_Align(cow, 3276800/3276800 bytes, 8 align) failed.  caller: 0x41800a84d6d1
vmkernel:  cpu9:00000000)WARNING: Cow: 549: No memory available! Called from 0x41800a84d6d1
vmkernel:  cpu9:0000000)Cow: 1759: Failed on handle 3 (75243021) of 4 with Out of memory

HostD Log entries:

[10:00.979 29486B90 info 'Libs'] Vix_TranslateMsgPostError: No translation found for error message "Cannot open the disk '/vmfs/volumes/519f966e-75ee85a7-c2c4-00151791f2bc/nrshrs0_1/server001-000003.vmdk' or one of the snapshot disks it depends on.
Reason: Cannot allocate memory.".


Try  to change Heap size to at maximum value 128MB for ESXi 4.1, after changing this value, ESXi need to restart the host to take effect and this process which might take 10 mins of downtime

Location of Heapsize:

  • Go to ESXi host
  • Go to configuration tab
  • Under software column, go to Advance Settings
  • New windows will pop up, on that windows go to VMFS3 tab
  • on right hand side, VMFS3.MaxHeapSizeMB changed its value to max (128)

Post your question or comment

No comments:

Post a Comment