From owner-freebsd-current@FreeBSD.ORG Tue Jan 20 17:31:43 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 13B2E16A4CE for ; Tue, 20 Jan 2004 17:31:43 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7551243D4C for ; Tue, 20 Jan 2004 17:31:32 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i0L1TXUd071737; Tue, 20 Jan 2004 20:29:33 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i0L1TX2W071734; Tue, 20 Jan 2004 20:29:33 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Tue, 20 Jan 2004 20:29:33 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Namik Dala In-Reply-To: <20040120144747.GB13132@snickers.dahoam> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org 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 01:31:43 -0000 On Tue, 20 Jan 2004, Namik Dala wrote: > I've upgraded to 5.2-RELEASE last days. Now NFS seems to be > broken. There is an NFS server and 2 NFS clients. The /home > partition is shared. If I start mutt on an NFS client it wants to > read the default mailbox (over NFS) and hangs: > > $ ps -auxww | fgrep mutt > namik 71553 0.0 1.0 4221 2312 p7 D+ 1:50AM 0:00.75 mutt > > Is this a known problem? And is there a workaround? Questions: (1) Are you using rpc.lockd on the client? Server? Are both clinet and server running 5.2-R? Are you using NFS over UDP, over TCP; NFSv2 or NFSv3? (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. There are some known issues involving NFS, most of them involving rpc.lockd. There are some other reports of NFS problems, but they've been hard to track down, as they appear to be very sensitive to the local configuration. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research