From owner-freebsd-net@FreeBSD.ORG Thu Jul 9 04:27:51 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BF1910656FC for ; Thu, 9 Jul 2009 04:27:50 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (mail.timing.com [206.168.13.218]) by mx1.freebsd.org (Postfix) with ESMTP id 52DD38FC17 for ; Thu, 9 Jul 2009 04:27:50 +0000 (UTC) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id n68LVVpB041218 for ; Wed, 8 Jul 2009 15:31:31 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.14.3/8.14.3) with ESMTP id n68LVTwp007108; Wed, 8 Jul 2009 15:31:29 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.14.3/8.14.3/Submit) id n68LVTjL007105; Wed, 8 Jul 2009 15:31:29 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19029.4145.296260.915327@gromit.timing.com> Date: Wed, 8 Jul 2009 15:31:29 -0600 From: John Hein To: net@freebsd.org X-Mailer: VM 7.19 under Emacs 22.3.1 X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on Daffy.timing.com X-Virus-Status: Clean Cc: Subject: network lock manager (lockd) deadlocked in 'rpcrecv' X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jul 2009 04:27:53 -0000 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.