• Powering on a virtual machine fails
• You cannot power on a virtual machine
• You see one of these error:
  
  • Error message: Failed to extend swap file (fileHandle xxxxx) from 0 KB to yyyyy KB: Invalid metadata.
    
    Could not power on VM : Invalid metadata. Failed to power on VM.
    
  • Could not power on VM : No space left on device
    Failed to power on VM.
    Failed to extend swap file from 0 KB to yyyyy KB.
    
    
• You can power on the virtual machine if setting a memory reservation to the same size as the RAM assigned to the virtual machine
• The VMkernel logs show messages similar to:

  Nov 15 11:46:18 esx02 vmkernel: 112:02:17:36.504 cpu0:108855)WARNING: VSCSI: 4129: Can't translate bad0099/Invalid metadata to SCSI: using MEDIUM ERROR
  Nov 15 11:46:45 esx02 vmkernel: 112:02:18:03.763 cpu2:108883)WARNING: FS3: 7552: Volume 4b0432c8-f4d6dae8-b086-002655826b48 ("Volume1") may be damaged on disk. Corrupt lock detected at offset c08b2d9e00050000: [type 12538 offset 13874233233673355264 v 13874233233703141290, hb o
  Nov 15 11:46:45 esx02 vmkernel: 112:02:18:03.763 cpu2:108883)WARNING: Swap: 2214: Failed to extend swap file: Invalid metadata, fileHandle 656212749, from 0KB to 4194304KB.

• Configure the ESX/ESXi host to create the swap file on another datastore.
  
• For more information, see Storing a virtual machine swap file in a location other than the default in ESX/ESXi (1004082).
  
  
• Create a memory reservation with the same size as the memory assigned to the virtual machine. This prevents the creation of a swap file.
  
• For more information, see the Resource Management Guide.

To workaround this issue when you see the error No space left on device, grow or add extents to the volume in question.