From owner-freebsd-stable@FreeBSD.ORG Mon Aug 28 10:11:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F0E616A4DE for ; Mon, 28 Aug 2006 10:11:19 +0000 (UTC) (envelope-from michael@araneidae.co.uk) Received: from mail.araneidae.co.uk (araneidae.co.uk [62.3.233.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id A34FD43D64 for ; Mon, 28 Aug 2006 10:11:15 +0000 (GMT) (envelope-from michael@araneidae.co.uk) Received: from saturn.araneidae.co.uk (localhost [127.0.0.1]) by mail.araneidae.co.uk (8.13.1/8.13.1) with ESMTP id k7SABE6f062126; Mon, 28 Aug 2006 10:11:14 GMT (envelope-from michael@araneidae.co.uk) Received: from localhost (michael@localhost) by saturn.araneidae.co.uk (8.13.1/8.13.1/Submit) with ESMTP id k7SABEjx062123; Mon, 28 Aug 2006 10:11:14 GMT (envelope-from michael@araneidae.co.uk) X-Authentication-Warning: saturn.araneidae.co.uk: michael owned process doing -bs Date: Mon, 28 Aug 2006 10:11:14 +0000 (GMT) From: Michael Abbott To: Kostik Belousov In-Reply-To: <20060827195555.GI79046@deviant.kiev.zoral.com.ua> Message-ID: <20060828095941.J62085@saturn.araneidae.co.uk> References: <20060827102135.B49194@saturn.araneidae.co.uk> <20060827135434.GH79046@deviant.kiev.zoral.com.ua> <20060827183903.G52383@saturn.araneidae.co.uk> <20060827195555.GI79046@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: NFS locking: lockf freezes (rpc.lockd problem?) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Aug 2006 10:11:19 -0000 On Sun, 27 Aug 2006, Kostik Belousov wrote: > On server, > tcpdump -p -s 1500 -w file -i host Ok. I've run saturn# tcpdump -p -s 1500 -w tcpdump.out -i xl0 host 10.0.0.105 and run the failing test on venus (with `rpc.lockd -d1`). The failing lockf has moved -- it took longer to fail this time -- but it does fail. As before, one of the lockd processes has vanished. venus# ps axlww | grep rpc\\. 0 18303 1 0 96 0 263460 916 select Ss ?? 0:00.00 /usr/sbin/rpc.statd -d 0 18308 1 0 96 0 1416 1024 select Is ?? 0:00.01 /usr/sbin/rpc.lockd -d1 1 18309 18308 0 4 0 1420 1036 nfsloc I ?? 0:00.00 /usr/sbin/rpc.lockd -d1 venus# ps axlww | grep rpc\\. 0 18303 1 0 96 0 263460 884 select Ss ?? 0:00.00 /usr/sbin/rpc.statd -d 1 18309 1 0 4 0 1440 1008 nfsloc S ?? 0:00.00 /usr/sbin/rpc.lockd -d1 > Yes, this is very interesting. Does something appears in the logs ? > Also, you shall use -d option of rpc.lockd (and show the output together > with tcpdump output). Well. See my previous message this smorning for -d output. As for tcpdump, I have an interesting (and rather obvious) problem: saturn# stat -f%z /tmp/tcpdump.out 161794058 Hmm. Perhaps you don't want that. I'll hang onto it for a bit: let me know what you want to do with it!