Date: Wed, 8 Jul 2009 15:31:29 -0600 From: John Hein <jhein@timing.com> To: net@freebsd.org Subject: network lock manager (lockd) deadlocked in 'rpcrecv' Message-ID: <19029.4145.296260.915327@gromit.timing.com>
next in thread | raw e-mail | index | archive | help
I have a home directory on FreeBSD 7.2-stable (20090705), amd64. It is serving up the directory over nfs (v3, tcp), and now I'm seeing lots of 'lockd not responding' on Fedora 10 & 11 systems. USER PID PPID SID NI %CPU %MEM VSZ RSS TT WCHAN STAT STARTED TIME COMMAND root 791 1 791 0 0.0 0.0 6748 1500 ?? rpcrec Ds 2:45PM 0:05.80 /usr/sbin/rpc.lockd Once lockd gets in this state, doing a test lock on a file from a FreeBSD box locks with 'lockd not responding', too (and ctrl-c and kill -9 does nothing). USER PID PPID SID NI %CPU %MEM VSZ RSS TT WCHAN STAT STARTED TIME COMMAND jhein 6297 3491 3491 0 0.0 0.0 1412 604 p5 nlmrcv T+ 3:18PM 0:00.00 /h/jhein/nfslocktest /nfs/locktest I see this on an i386 6.4-stable, too.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19029.4145.296260.915327>