Troubleshooting the error: Operation failed, diagnostics report

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

Summary

• If you try to extend an ATS (Atomic Test & Set ) only datastore with a non-ATS LUN, you see the error:
  
  Operation failed, diagnostics report: Unable to add extent to filesystem
  
  
• You see the error:
  
  Operation failed, diagnostics report: Sysinfo error on operation returned status : Bad parameter. Please see the VMkernel log for detailed error information

Impact

• If you see the error Unable to add extent to filesystem , you cannot extend the ATS-only datastore.
  
  
• If you see the error Sysinfo error on operation returned status : Bad parameter. Please see the VMkernel log for detailed error information , virtual machine performance may be affected.

extend-ats-datastore extend-atomic-test-set-datastore ats-extent

Environment

VMware ESXi 4.1.x Installable
VMware ESXi 4.1.x Embedded
VMware vSphere ESXi 5.0
VMware ESX 4.1.x

Resolution

The error Unable to add extent to filesystem occurs because extending an ATS-only datastore with a non-ATS LUN is not supported.

Note: For further information on Atomic Test & Set (ATS), see vStorage APIs for Array Integration FAQ (1021976).

The error Sysinfo error on operation returned status : Bad parameter. Please see the VMkernel log for detailed error information occurs if DRS generates a new set of resource settings for a given resource pool but vpxa is not able to apply them to the virtual machines. This can happen if the virtual machine is in a state where resource update is not allowed (for example, it is in the middle of a migration or a VCB backup).

If this message occurs for an extended period of time, research further into the cause. If the virtual machine is in the middle of an operation, you can ignore the message.

If the virtual machine is not in a state that prevents the resource update, then the resource setting that DRS generated has a circular dependency. This issue is resolved in ESXi 5.x. To workaround this issue in ESX/ESXi 4.1, set the parent resource pool to expandable instead of limited.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box