From owner-freebsd-current@FreeBSD.ORG Thu Dec 23 04:27:29 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 80A0416A4CE for ; Thu, 23 Dec 2004 04:27:29 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F2FD43D49 for ; Thu, 23 Dec 2004 04:27:27 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iBN4QLVn025703 for ; Thu, 23 Dec 2004 14:56:21 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Thu, 23 Dec 2004 14:57:17 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iBN4O0Q07427 for ; Thu, 23 Dec 2004 14:54:00 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK37D6BK; Thu, 23 Dec 2004 14:53:56 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iBN4O4Rj005428 for ; Thu, 23 Dec 2004 14:54:04 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iBN4O4dr005427 for freebsd-current@freebsd.org; Thu, 23 Dec 2004 14:54:04 +1030 (CST) (envelope-from wilkinsa) Date: Thu, 23 Dec 2004 14:54:04 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041223042404.GB5393@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <20041221055157.5bf808ff@dolphin.local.net> <20041222202941.79ea15a6@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041222202941.79ea15a6@dolphin.local.net> User-Agent: Mutt/1.5.6i 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 04:27:29 -0000 0n Wed, Dec 22, 2004 at 08:29:41PM -0600, Conrad J. Sabatier wrote: >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. What is the "new direct i/o mode for nfs" all about ? - aW