We are running FDB on a OCP cluster which run in a managed-nfs which is based on vSphere (VMWare).
All the pods that created PVC failed. In the trace log, I see this:
We can login to the pod and create file under the data directory without issue but fdbserver failed to do that. We see the processID.part with a size of 0 meaning the fdbserver can only create a file name but failed to create the file at all. Any idea what is needed for NFS to set? We have tried setting (no_root_squash) and that does not help. fdbserver is running as a local ID and we have logged in with that id and write the file in the dataDir without any issue.
We are seeing these in the trace log:
<Event Severity=“10” Time=“1688582799.174804” DateTime=“2023-07-05T18:46:39Z” Type=“AsyncFileEIORenameError” ID=“0000000000000000” Filename=“/var/fdb/data/processId” UnixErrorCode=“10” UnixError=“Device or resource busy”
It seems the AsyncFIleEIOREnameError means it can’t rename the file while it is being written? The file in question is the processID, we can see it as processID.part and have a size of zero. Normally, it should contain a small binary number.
Any help or suggestion are much appreciated