.iorm.sf/access events in ESXi 6.0 host syslogs (across clusters and storage arrays)

[stacycarter]

I noticed that the events below appear in the syslog of our ESXi 6.0 hosts frequently.  Our hosts have been connected to NFS datastores for a long time, and SIOC is not (and unfortunately cannot) be enabled at this time.  Seeing these on hosts across clusters that are attached to different storage arrays.  No constant storage issues happening in our environment.  Are these normal?  Just starting to use Log Insight, so it's possible these events have been there all along.

sdrsInjector: open /vmfs/volumes//datastorename/.iorm.sf/access(0x241, 0x0) failed: No such file or directory

storageRM: open /vmfs/volumes//datastorename/.iorm.sf/access(0x241, 0x0) failed: No such file or directory

[hypervisorboy]

Hi stacycarter ,

I don't think it's an issue if SIOC is disabled (it's pretty normal ) because .iorm.sf file has been created by SIOC. it can't access because there is no file.

sdrsinjector.log file is vSphere Storage DRS  log which shows this message when DRS takes place and try to use SIOC file for placing of host/datastore recommendation.

SIOC log file is (storagerm.log) .so storagerm will show this message when it tries to use this place for datastore recommendation or any other task. (obvious).