kern/95247: NFS file locking problem,
rpc.lockd seems to be leaking ports?
girgen at FreeBSD.org
Mon Apr 3 01:50:17 UTC 2006
>Synopsis: NFS file locking problem, rpc.lockd seems to be leaking ports?
>Arrival-Date: Mon Apr 03 01:50:16 GMT 2006
>Originator: Palle Girgensohn <girgen at FreeBSD.org>
>Release: FreeBSD 6.1-PRERELEASE i386
Ping Pong AB
System: FreeBSD rambutan.pingpong.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #1: Tue Mar 21 13:42:51 CET 2006 girgen at rambutan.pingpong.net:/usr/obj/.a/banan/usr/src/sys/WORKSTATION i386
(This PR is probably related to kern/84953)
I'm having a problem with rpc.lockd
Clients are mainly FreeBSD 5.4-stable, server is FreeBSD-4.11-RELEASE-p13.
/home is nfs mounted via amd.
rpc.statd and rpc.lockd is on for both clients and server
Since we started using eclipse (which requires file locking to
operate) we get problems where the number of open priviledged UDP
ports on the server are exhausted.
running sockstat | grep rpc.lock show over 400 lines like this:
root rpc.lock 174 440 udp4 *:580 *:*
The default setting for FreeBSD-4.11 seems to be a portrange of 400
ports, I've bumped this by lowering net.inet.ip.portrange.lowlast from
600 -> 500, but eventually they will all be in use too. I have not
found good way to free them properly apart from rebooting the server.
All nfs traffic is UDP only, perhaps that is a problem?
nfsiod -n 4 on all clients
nfs_server_flags="-u -n 12" on the server, perhaps it is too low?
There are only six workstations attached to the server. Each have
about ten rpc.lockd sockets open, while the server has about 400, so
it seems to be a leakage in the server?
See also kern/84953.
More information about the freebsd-bugs