From owner-freebsd-current@FreeBSD.ORG Thu Dec 23 02:31:52 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 99FB616A4CE for ; Thu, 23 Dec 2004 02:31:52 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17BAB43D31 for ; Thu, 23 Dec 2004 02:31:52 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.50]) by lakermmtao05.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041223022950.ILGV16431.lakermmtao05.cox.net@dolphin.local.net> for ; Wed, 22 Dec 2004 21:29:50 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id iBN2TkVM089060 for ; Wed, 22 Dec 2004 20:29:46 -0600 (CST) (envelope-from conrads@cox.net) Date: Wed, 22 Dec 2004 20:29:41 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20041222202941.79ea15a6@dolphin.local.net> In-Reply-To: <20041221055157.5bf808ff@dolphin.local.net> References: <20041221055157.5bf808ff@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: NFS flakiness since @ last Friday 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: Thu, 23 Dec 2004 02:31:52 -0000 On Tue, 21 Dec 2004 05:51:57 -0600, "Conrad J. Sabatier" wrote: > I'm seeing some real instability in NFS since approximately last > Friday. Intermittently, I'm seeing messages such as the following: > > On the client machine: > > Dec 20 23:18:22 dolphin kernel: impossible packet length (1820291) > from nfs server gateway:/mm > Dec 21 00:51:47 dolphin kernel: impossible packet length (1746474142) > from nfs server gateway:/mm > > and > > Dec 21 01:14:41 dolphin kernel: nfs send error 35 for server > gateway:/mm Dec 21 01:16:33 dolphin kernel: nfs send error 35 for > server gateway:/mm Dec 21 01:16:38 dolphin kernel: nfs send error 35 > for server gateway:/mm Dec 21 01:16:40 dolphin kernel: nfs server > gateway:/mm: not responding Dec 21 01:16:43 dolphin kernel: nfs server > gateway:/mm: is alive again > > On the server machine: > > Dec 20 21:52:48 gateway kernel: nfsd send error 32 > Dec 20 21:57:50 gateway kernel: nfsd send error 32 > Dec 20 22:00:45 gateway kernel: nfsd send error 32 > Dec 20 22:23:29 gateway kernel: nfsd send error 32 > Dec 20 23:18:23 gateway kernel: nfsd send error 32 > > Then, ultimately, all NFS communication just breaks down > altogether until a reboot. > > I'm also seeing "sillyrenames" left behind occasionally in nfs-mounted > directories. > > There were a couple of nfs-related commits last Thursday, which I > believe are most likely the culprit, although I don't know which ones > exactly. I do believe this problem is related to the new direct i/o mode for nfs. Disabling it seems to have made the problem disappear. -- Conrad J. Sabatier -- "In Unix veritas"