VM Creation Fails on vSAN ESA Stretched Cluster with RAID-6 Local Policy : Cannot complete file creation operation. Failed to create object.

Products

• VMware vSAN

Issue/Introduction

 

• VPXD logs show: key = "vob.vsanprovider.object.creation.failed", message = "Failed to create object."
• Cluster is a Stretched Cluster (e.g., 4 hosts at Site A, 4 hosts at Site B).
• VM Storage Policy is set to Dual Site Mirroring with Local FTT=2 (RAID-6).

 

 

Environment

 

• vSAN 8.0 ESA
• Stretched Cluster topology

 

Cause

The VM Storage Policy (RAID-6/Local FTT=2) requires a minimum of 6 hosts per site to satisfy data and parity placement rules. In a 4-host-per-site geometry, vSAN ESA cannot fulfill the RAID-6 components locally, leading to object creation failure.

Resolution

Update the VM Storage Policy to align with the physical host count per site:

1. Navigate to Policies and Profiles > VM Storage Policies.
2. Edit the impacted policy.
3. Set Site disaster tolerance to Dual site mirroring.
4. Set Failures to tolerate to 1 failure - RAID-5 (Erasure Coding).
5. Apply the policy.

vSAN ESA utilizes adaptive RAID-5, which dynamically forms a 2+1 stripe to accommodate the 4-host-per-site limitation while maintaining erasure coding efficiency.

For updates on vSAN ESA architectural guidelines, refer to this article.

Refer: vSAN ESA Storage Policy Management

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support