From owner-freebsd-current@FreeBSD.ORG Wed Jan 21 08:47:19 2004 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 47AC016A4CE for ; Wed, 21 Jan 2004 08:47:19 -0800 (PST) Received: from mail-in-04.arcor-online.net (mail-in-04.arcor-online.net [151.189.21.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D89C43D2F for ; Wed, 21 Jan 2004 08:47:18 -0800 (PST) (envelope-from freebsd-current@nada.refused.cc) Received: from dialup.user (dsl-213-023-020-161.arcor-ip.net [213.23.20.161]) by mail-in-04.arcor-online.net (Postfix) with ESMTP id 150C16D37BE for ; Wed, 21 Jan 2004 17:47:16 +0100 (CET) Received: by localhost (Postfix, from userid 100) id 69F5DD14; Wed, 21 Jan 2004 17:47:12 +0100 (CET) Date: Wed, 21 Jan 2004 17:47:12 +0100 From: Namik Dala To: current@freebsd.org Message-ID: <20040121164711.GB28644@snickers.dahoam> Mail-Followup-To: current@freebsd.org References: <20040120144747.GB13132@snickers.dahoam> <20040121022923.GB17110@snickers.dahoam> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040121022923.GB17110@snickers.dahoam> User-Agent: Mutt/1.5.5.1i Subject: Re: NFS: Processes marked "in disk" 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: Wed, 21 Jan 2004 16:47:19 -0000 On Wed, Jan 21, 2004 at 03:29:23AM +0100, Namik Dala wrote: > On Tue, Jan 20, 2004 at 08:29:33PM -0500, Robert Watson wrote: > > (2) Could you show the output of "ps -axl" for hung processes? Might also > > be interesting to have you recompile the kernel with "options DDB" > > and "options BREAK_TO_DEBUGGER". When a process hangs on the client, > > hit ctrl-alt-escape (or serial break on serial console), then type in > > 'trace pid', substituting the pid of the process in question. > > If it dies again, I will do this. Hmm.. bad idea, or not? The problem is that the rpc.lockd parent on the server side has core dumped. May be I should figure out how to compile it with debugging symbols and send a backtrace if it happens again. -Namik-