"Name [catalog] not found in directory" in osfsd.log is benign

Products

• VMware vSAN

Issue/Introduction

• The following messages are recorded to /var/run/log/osfsd.log.
  
  YYYY-MM-DDTHH:MM:SSZ In(14) osfsd[#######]: [ sub=Vmklink opID=####] BEGIN vmklink 0x####, type:LOOKUP, pid:[    vsan], cid:################-################, aid:################-################, bufLen:0, fileName:catalog
  YYYY-MM-DDTHH:MM:SSZ In(14) osfsd[#######]: [ opID=####] Adding a thread to threadpool osfsd-nvsan
  YYYY-MM-DDTHH:MM:SSZ In(14) osfsd[#######]: [ opID=####][ opID=8917] Added a new thread to threadpool (osfsd-nvsan), numThreadsInPool (1)
  YYYY-MM-DDTHH:MM:SSZ In(14) osfsd[#######]: [] Starting main loop for the worker thread osfsd-nvsan
  YYYY-MM-DDTHH:MM:SSZ Er(11) osfsd[#######]: [ opID=####] Name [catalog] not found in directory, clusterUuid: ########-####-####-####-############, cid: ########-####-####-####-############

• vSAN File Service is disable in your environment.

Environment

VMware vSAN

Cause

The catalog directory contains metadata related to vSAN File Service.
The catalog directory doesn't exist when vSAN File service is disabled.

Resolution

The behavior is expected.
The messages is harmless and can be safely ignored.

Additional Information

osfsd.log に "Name [catalog] not found in directory"という無害なエラーが記録される