From owner-freebsd-current Mon Mar 1 17:54:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from speed.rcc.on.ca (radio163.mipps.net [205.189.197.163]) by hub.freebsd.org (Postfix) with SMTP id 374C4153B2 for ; Mon, 1 Mar 1999 17:54:05 -0800 (PST) (envelope-from tr49986@rcc.on.ca) Received: from a35 ([207.164.233.121]) by speed.rcc.on.ca (8.6.12/8.6.9) with SMTP id WAA32221 for ; Mon, 1 Mar 1999 22:07:41 -0500 Message-ID: <004f01be644f$239ae3e0$2300000a@a35.my.intranet> From: "RT" To: Subject: Still NFS Problems Date: Mon, 1 Mar 1999 20:51:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 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? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message