NFSv3: NFS client receives 'Error (37): No locks available' when trying to lock a file

Solution Verified - Updated -

Issue

  • NFS client can not lock files using NFSv3.
  • NFS client can lock a file using NFSv4.x
  • Attempted file locks receive Error (37): No locks available
  • Packet captures show no NLM LOCK Calls.
  • rpcbind on the NFS client is logging messages such as:
Jun 12 14:31:21 client.example.net rpcbind[11809]: cannot get local address for udp: Servname not supported for ai_socktype
Jun 12 14:31:21 client.example.net rpcbind[11809]: cannot get local address for tcp: Servname not supported for ai_socktype
  • rpcbind shows no listening sockets in # lsof output

Environment

  • Red Hat Enterprise Linux
  • NFSv3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content