From owner-freebsd-current@FreeBSD.ORG Mon May 12 14:01:47 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A52137B404; Mon, 12 May 2003 14:01:47 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CB4843FDD; Mon, 12 May 2003 14:01:45 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h4CL1dOn057335; Mon, 12 May 2003 17:01:39 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h4CL1dgk057332; Mon, 12 May 2003 17:01:39 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 12 May 2003 17:01:39 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Don Lewis In-Reply-To: <200305122039.h4CKdMM7048544@gw.catspoiler.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: alfred@FreeBSD.org cc: current@FreeBSD.org Subject: Re: rpc.lockd spinning; much breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2003 21:01:47 -0000 On Mon, 12 May 2003, Don Lewis wrote: > > The rpc.lockd process remains extremely busy even after crash2 is rebooted > > and the stream of packets is no longer present. > > > > I'm not sure how to go about debugging these problems, but the current > > scenario basically means I can't get both the crash boxes through their > > daily events if both the client and server are very busy (i.e., if they > > both run their daily events at the same time). I'm going to reboot cboss > > and the systems and see if that flushes whatever nasty state hangs around, > > but any advice on the debugging process would be helpful. Is there a way > > to get rpc.lockd on the server to dump it's state to a file? > > Why not attach the process in gdb and step through the code to find the > loop? Well, I guess the problem is I'm not familiar with the NFS lock manager protocol, and what I'm looking for more is debugging advice: is the best approach to attach to the client or server rpc.lockd? I had a lot of trouble getting ethereal to work well for debugging NLM stuff as it tended to crash. :-) Things are somewhat complicated by the fact that once you lose the rpc.lockd on a client, lots of programs begin to hang and stack up... Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories