What I know about Solaris 10 NFS server file lock limits
June 12, 2009
Suppose that you have a Solaris fileserver and a bunch of NFS clients
(in this case they're Linux machines, but I don't think it matters).
Perhaps one or two of them are Samba servers. Further suppose that your
client machines start reporting things like '
(We'll assume that you use tools like
Although it's dangerous to extrapolate from current OpenSolaris code (and the lack of documented tuneable parameters), it seems as if Solaris 10 has no intrinsic limit on how many file locks it supports; if you ask for too many for the system to handle, your processes just start going to sleep as they wait for kernel memory to be freed up.
However, there does appear to be a limit on how many concurrent NFS
locking requests the server will handle; this is the setting for
(It's also possible that you can run into this if the server is short of memory in general, so that the NFS locking requests start running into the 'sleep waiting for kernel memory' issue, clogging up this limited supply of threads.)
From our experience, using
Written on 12 June 2009.
* * *
Atom feeds are available; see the bottom of most pages.