NFS Locking Potential Issue

Hi All,

My first post here so big Hi to everyone.

I need some guidance related to NFS locking I think I have a problem with the newest version of Scale. In my Red Hat OpenShift cluster my pod throwing an error:

2024-11-12T12:01:13.846Z FATAL	cmd/keeper.go:2086	cannot take exclusive lock on data dir "/stolon-data/pg/lock": resource temporarily unavailable

I’m trying to use TrueNas as NFS storage for my OpenShift cluster, and looking on IBM documentation they saying that following settings need to be enabled on exported NFS share:

    - rw
    - sync
    - no_root_squash
    - no_subtree_check

I cannot see an easy way to validate these settings from the Web interface so is there a way to ex-check some export files on the TrueNas server are these settings set up? That’s what I want to confirm now.

My current settings are (apart from defaults):

  • For service: Enabled only NFSv4 and Allow non root mount
  • For share: Maproot user set to root and maproot group to wheel + of course allowed network

Can anyone give me some advise Is I even looking into right direction?

Many thanks
D