From owner-freebsd-current Sun Feb 21 22:10:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles184.castles.com [208.214.165.184]) by hub.freebsd.org (Postfix) with ESMTP id 2494B10E01 for ; Sun, 21 Feb 1999 22:10:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA01966; Sun, 21 Feb 1999 22:05:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902220605.WAA01966@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "RT" Cc: current@FreeBSD.ORG Subject: Re: NFS Problems In-reply-to: Your message of "Sun, 21 Feb 1999 22:11:13 EST." <003901be5e11$02748c00$0a00000a@a19.my.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Feb 1999 22:05:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I update 3-Stable nearly weekly, and have been experiencing the same problem > for quite a while now. NFS imports, on the client side appear to be losing > data. When this occurs, I see .nfs78969 files on the server side. These files exist because they've been deleted but not closed; this is probably just an artifact of the program being stuck. > The > program on the client side always freezes (top reports it's STAT as 'D'). You need to pass the 'l' switch to ps and look at the 'wchan' column to see where it's actually stuck. > Are there some switches I should try? I assume (without testing) that > 4-current would also show the same problems as 3-stable. Which is why I > posted here. There have actually been some changes in 4.0 which might affect this, if I understand correctly. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message