From owner-freebsd-bugs Thu Dec 24 18:10:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20561 for freebsd-bugs-outgoing; Thu, 24 Dec 1998 18:10:14 -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 SAA20539 for ; Thu, 24 Dec 1998 18:10:11 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id SAA19238; Thu, 24 Dec 1998 18:10:01 -0800 (PST) Date: Thu, 24 Dec 1998 18:10:01 -0800 (PST) Message-Id: <199812250210.SAA19238@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: sysadmin@mfn.org Subject: Re:kern/6914:FreeBSD2.2.6-RELEASEandNFSisUNSTABLE Reply-To: sysadmin@mfn.org Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/6914; it has been noted by GNATS. From: sysadmin@mfn.org To: freebsd-gnats-submit@freebsd.org, froden@bigblue.no Cc: Subject: Re:kern/6914:FreeBSD2.2.6-RELEASEandNFSisUNSTABLE Date: Thu, 24 Dec 1998 20:03:44 -0600 (CST) We have noticed this as well, under 2.2.5-R. The only indication we ahve seen *reliably* is that the NFS clients seem to hang in state NFSAIO. In addition, we have noticed a great deal of "nfs server ... not responding" messages which are *immediately* followed by "nfs server ok" messages. These appear so fast as to have the same timestamps, yet the clients are still in NFSAIO, and the file systems are unresponsive. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message