From owner-freebsd-current Mon Mar 1 20: 5:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 922F3155CC for ; Mon, 1 Mar 1999 20:05:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA50086; Mon, 1 Mar 1999 20:05:07 -0800 (PST) (envelope-from dillon) Date: Mon, 1 Mar 1999 20:05:07 -0800 (PST) From: Matthew Dillon Message-Id: <199903020405.UAA50086@apollo.backplane.com> To: "RT" Cc: Subject: Re: Still NFS Problems References: <004f01be644f$239ae3e0$2300000a@a35.my.intranet> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In the past 3 weeks I've upgraded from 3.0-release, to 3-stable to 4-current :(as of 4 days ago). I've tried nfs v2 and nfs v3. In all of those :circumstances I end up with programs locking due to write problems. : :I'm no good a debugging, so if someone could hold my hand through this :one... : :Basic problem. .nfs798798 files appearing on server, program on client :locks up in STAT 'D' according to top. The problem only occurs on read / :write mounts (duh..). I only have my home partition writable as of right :now. : :The easiest way to replicate it is to compile something large. i.e. make :world from the client machine. Soon I'll just make my home directory read :only too :) Any ideas? fixes? things I can show you? When this happens, run 'dmesg' on the client. Does it report any problems near the end of the system messages? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message