From owner-freebsd-bugs Wed Jan 20 17:10:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15339 for freebsd-bugs-outgoing; Wed, 20 Jan 1999 17:10:06 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15308 for ; Wed, 20 Jan 1999 17:10:01 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id RAA15910; Wed, 20 Jan 1999 17:10:02 -0800 (PST) Date: Wed, 20 Jan 1999 17:10:02 -0800 (PST) Message-Id: <199901210110.RAA15910@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: "Slowbob" Subject: Re: kern/7619: odd nfs server not responding messages appear Reply-To: "Slowbob" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/7619; it has been noted by GNATS. From: "Slowbob" To: Cc: Subject: Re: kern/7619: odd nfs server not responding messages appear Date: Sun, 20 Dec 1998 03:30:38 -0600 We also have this problem, under 2.2.5-R clients and servers, but we have noticed that this message is emitted while the clients are in NFSAIO state. As per the trouble report, there is no sign that anything is amiss during the periods when errors are emitted, however, we also have periods of long pauses (ranging anywhere from a few seconds to over a minute) on NFS. During these pauses, there are *no* error messages emitted at all, either during or after the pause. The only thing we have tracked down for sure is that the NFS clients are stuck in the same NFSAIO state during the pause as appears when the above error messages are emitted. Just a clarification: the time interval for the error messages (here at least) is *always* timestamped 3 seconds apart (i.e., 00:00:00 for the not responding error, 00:00:03 for the Alive again message) - clue?? Yours, J.A. Terranson sysadmin@mfn.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message