From owner-freebsd-current  Wed Jan  7 11:08:17 1998
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA28815
          for current-outgoing; Wed, 7 Jan 1998 11:08:17 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28804
          for <current@freebsd.org>; Wed, 7 Jan 1998 11:08:06 -0800 (PST)
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.5/8.8.5) id NAA13990;
	Wed, 7 Jan 1998 13:07:53 -0600 (CST)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199801071907.NAA13990@home.dragondata.com>
Subject: Re: New NFS saga
In-Reply-To: <19980106144429.24420@mcs.net> from Karl Denninger at "Jan 6, 98 02:44:29 pm"
To: karl@mcs.net (Karl Denninger)
Date: Wed, 7 Jan 1998 13:07:53 -0600 (CST)
Cc: current@freebsd.org
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> So back it out to 1.41 and see if the problem goes away.
> 

1.41 seems essentially the same as current, but I tried anyway...

Up less than 1 hour and: 'panic: fault on no fault entry' with *tons* of 'no
buffer space available' errors in syslog.

I don't think the new vm stuff is too happy with nfs. :)


Kevin