Cannot enable Storage IO Control on the datastore with extents
search cancel

Cannot enable Storage IO Control on the datastore with extents

book

Article ID: 342621

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
Error : "The operation is not supported on the object" When enabling Storage IO Control (SIOC) on datastore.

vpxd.log  shows below errors 

2019-01-30T07:54:19.393Z error vpxd[7F2BD470E700] [Originator@6876 sub=drmLogger opID=EditDatastoreCapabilitiesFormMediator-applyOnMultiEntity-33042372-ngc:74047227-85] [ConfigureDatastoreIORMCheck] type not supported: VMFS 
2019-01-30T07:54:19.393Z info vpxd[7F2BD470E700] [Originator@6876 sub=vpxLro opID=EditDatastoreCapabilitiesFormMediator-applyOnMultiEntity-33042372-ngc:74047227-85] [VpxLRO] -- FINISH task-780494 
2019-01-30T07:54:19.393Z info vpxd[7F2BD470E700] [Originator@6876 sub=Default opID=EditDatastoreCapabilitiesFormMediator-applyOnMultiEntity-33042372-ngc:74047227-85] [VpxLRO] -- ERROR task-780494 -- StorageResourceManager -- vim.StorageResourceManager.ConfigureDatastoreIORM: vmodl.fault.NotSupported: 
--> Result: 
--> (vmodl.fault.NotSupported) { 
--> faultCause = (vmodl.MethodFault) null, 
--> faultMessage = <unset> 
--> msg = "" 
--> } 
--> Args: 
--> 
--> Arg datastore: 
--> 'vim.Datastore:daf7e6cb-ac25-496c-9690-eaa51f149b01:datastore-262101' 
--> Arg spec: 
--> (vim.StorageResourceManager.IORMConfigSpec) { 
--> enabled = true, 
--> congestionThresholdMode = "automatic", 
--> congestionThreshold = 30, 
--> percentOfPeakThroughput = 90, 
--> statsCollectionEnabled = true, 
--> reservationEnabled = <unset>, 
--> statsAggregationDisabled = false, 
--> reservableIopsThreshold = <unset> 
--> }

Environment

VMware vSphere ESXi 6.0
VMware vSphere ESXi 7.x
VMware vSphere ESXi 6.7
VMware vSphere ESXi 8.0.x
VMware vSphere ESXi 6.5

Cause

SIOC is not supported on VMFS datastores that are constructed from multiple LUNs. This is because only a single LUN holds the metadata for the entire datastore and that is the only LUN that is monitored for failure. If any other LUN goes down, SIOC will be unaware of this change.

This can also occur if the same LUN is presented to the ESXi hosts in the cluster with different LUN IDs.

Resolution

1. Verify if the VMFS datastore where we are attempting to enable SIOC is not a multi-extent datastore.
2. Avoid same LUN presentation to the ESXi hosts in the cluster with different LUN IDs.