aws-fsx-openzfs-csi-driver icon indicating copy to clipboard operation
aws-fsx-openzfs-csi-driver copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

NFSv3 Mounts fail unless the --nolock mount option is specified

Open hughdanliu opened this issue 9 months ago • 3 comments

/kind bug

What happened? I attempted to mount an FSx for OpenZFS file system on an application pod using NFSv3 and received this error:

Output: mount.nfs: rpc.statd is not running but is required for remote locking. mount.nfs: Either use '-o nolock' to keep locks local, or start statd. mount.nfs: mounting ___ failed, reason given by server: No such file or directory

Even though the rpc-statd service was running on the node. What you expected to happen? NFSv3 mounts succeed without needing to provide the nolock mount option.

How to reproduce it (as minimally and precisely as possible)? Attempt to mount a file system using NFSv3

Anything else we need to know?: Nope

Environment

  • Kubernetes version (use kubectl version): 1.24
  • Driver version: v1.1.0

hughdanliu avatar May 08 '24 14:05 hughdanliu