topic System Read Lock table in Operating System - HP-UX

System Read Lock table

Manohar Manne_1 — Fri, 08 Feb 2002 15:11:36 GMT

On HPUX11 one of my thrid party application was failed due to error code 46. ( system record Lock table full). But I monitor the nflocks usage by glance only 3380 is using (total available is 10650). What could be the reason for error code 46. DO I need to tune any other kernel values.
TIA
Manohar

Re: System Read Lock table

A. Clay Stephenson — Fri, 08 Feb 2002 15:18:38 GMT

By any chance, are any of these NFS files? fcntl can set errno if there are problems getting locks on NFS mounted files.

Re: System Read Lock table

James R. Ferguson — Fri, 08 Feb 2002 15:25:17 GMT

Hi:

This is a somewhat unusual error. errno=46 is ENOLCK.

The man pages (for 'errno') note:

/begin_quote/

System lock table is full. Too many files have file locks on them, or there are too many record locks on files, or there are too many instances of a reading or writing process sleeping until an enforcement mode lock clears. This error may also indicate system problems in handling a lock request on a remote NFS file. This error is also currently returned for all attempts to perform locking operations on a remote NFS file that has its locking enforcement mode bit set, since the stateless nature of NFS prevents maintaining the necessary lock information.

/end_quote/

Since you do not see a high-water mark met, are there any NFS mounts involved, perhaps?

Regards!

...JRF...