Search the VMware Knowledge Base (KB)
View by Article ID

"Cannot complete file operation" error during vSAN VM creation (2105091)

  • 6 Ratings
Language Editions

Symptoms

Creating a virtual machine on a vSAN (formerly known as Virtual SAN) datastore fails with this error in the vSphere Web Client:

Cannot complete file creation operation

Note: For additional symptoms and log entries, see the Additional Information section.

Purpose

Enabling HardwareAcceleratedLocking on all ESXi hosts resolves the issue.

Cause

This issue occurs if the vStorage APIs for Array Integration (VAAI) primitive HardwareAcceleratedLocking is disabled.
vSAN uses Atomic Test & Set (ATS) to communicate with physical disks. ATS is one of the vStorage APIs for Array Integration (VAAI) primitives controlled by the HardwareAcceleratedLocking setting. This may be intentional or unintentional. For example, if an incorrect host profile is applied to the ESXi host, it may toggle this advanced setting.

Resolution

To resolve this issue, ensure that the HardwareAcceleratedLocking VAAI primitive is enabled on on all ESXi hosts participating in the vSAN cluster.

To enable the HardwareAcceleratedLocking VAAI primitive on your ESXi hosts:

  1. Connect to the ESXi host using SSH. For more information, see Using ESXi Shell in ESXi 5.x and 6.0 (2004746).
  2. Run this command to enable the required VAAI primitive:

    # esxcli system settings advanced set -i 1 -o /VMFS3/HardwareAcceleratedLocking 

    Note: This does not require a host reboot.

  3. Repeat steps 1 and 2 for each host in your vSAN cluster.

Additional Information

You experience these additional symptoms:
  • In the /var/log/vpxa.log file while the virtual machine creation task is running, you see errors similar to:

    <YYYY-MM-DD>T<TIME>.212Z [FFB1DB70 info 'Default' opID=514D5B8B-000111B3-4c-d-2f-51-56] [VpxLRO] -- ERROR task-internal-332 --  -- vpxapi.VpxaService.reserveName: vim.fault.CannotCreateFile:

    --> Result:
    --> (vim.fault.CannotCreateFile) {
    -->    dynamicType = <unset>,
    -->    faultCause = (vmodl.MethodFault) null,
    -->    file = "Failed to compute path for created directory (parent: vsan:52170593bf229c7e-94f5a45876ac0f41, file: 7d1eb954-64ad-6962-c0f1-90e2ba84217c",
    -->    msg = "Received SOAP response fault from [<cs p:1f3b3828, TCP:localhost:8307>]: CreateDirectory
    --> Cannot complete file creation operation.

  • In the /var/log/vmkernel.log file while the virtual machine creation task is running, you see entries similar to:

    <YYYY-MM-DD>T<TIME>.077Z cpu10:40374)WARNING: HBX: 2352: Failed to initialize VMFS distributed locking on volume 54b91e7f-fec7eed0-a588-90e2ba84217c: Not supported
    <YYYY-MM-DD>T<TIME>.198Z cpu10:40374)Vol3: 2769: Failed to get object 28 type 1 uuid 54b91e7f-fec7eed0-a588-90e2ba84217c FD 0 gen 0 :Not supported
    <YYYY-MM-DD>T<TIME>.198Z cpu10:40374)WARNING: Fil3: 2415: Failed to reserve volume f530 28 1 54b91e7f fec7eed0 e290a588 7c2184ba 0 0 0 0 0 0 0
    <YYYY-MM-DD>T<TIME>.198Z cpu10:40374)Vol3: 2769: Failed to get object 28 type 2 uuid 54b91e7f-fec7eed0-a588-90e2ba84217c FD 4 gen 1 :Not supported

Tags

VAAI HardwareAcceleratedLocking disabled, vSAN ATS VAAI, cannot complete file operation

See Also

Update History

08/05/2016 - Added Virtual SAN 6.0, 6.1 and 6.2 to Products.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 6 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 6 Ratings
Actions
KB: