Date: Thu, 31 Aug 2006 23:14:42 +0200 From: Greg Byshenk <gbyshenk@byshenk.net> To: Michael Abbott <michael@araneidae.co.uk> Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) Message-ID: <20060831211442.GQ633@core.byshenk.net> In-Reply-To: <20060829165820.F83998@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827202803.GP633@core.byshenk.net> <20060828082047.J61842@saturn.araneidae.co.uk> <20060828100942.GF20390@deviant.kiev.zoral.com.ua> <20060829165820.F83998@saturn.araneidae.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 29, 2006 at 05:05:26PM +0000, Michael Abbott wrote: [I wrote] > >>>An alternative would be to update to RELENG_6 (or at least RELENG_6_1) > >>>and then try again. > So. I have done this. And I can't reproduce the problem. > # uname -a > FreeBSD venus.araneidae.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon Aug 28 > 18:32:17 UTC 2006 > root@venus.araneidae.co.uk:/usr/obj/usr/src/sys/GENERIC i386 > Hmm. Hopefully this is a *good* thing, ie, the problem really has been > fixed, rather than just going into hiding. > So, as far as I can tell, lockf works properly in this release. Just as an interesting side note, I just experienced rpc.lockd crashing. The server is not running RELENG_6, but RELENG_5 (FreeBSD 5.5-STABLE #15: Thu Aug 24 18:47:20 CEST 2006). Due to user error, someone ended up with over 1000 processes trying to lock the same NFS mounted file at the same time. The result was over 1000 "Cannot allocate memory" errors followed by rpc.lockd crashing. I guess the server is telling me it wants an update... -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060831211442.GQ633>