From owner-freebsd-current  Wed May  8 11:49:08 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id LAA03463
          for current-outgoing; Wed, 8 May 1996 11:49:08 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA03456
          for <current@FreeBSD.org>; Wed, 8 May 1996 11:49:05 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA26483; Wed, 8 May 1996 11:38:51 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199605081838.LAA26483@phaeton.artisoft.com>
Subject: Re: NFS in -current is _BUSTED_
To: msmith@atrad.adelaide.edu.au (Michael Smith)
Date: Wed, 8 May 1996 11:38:50 -0700 (MST)
Cc: current@FreeBSD.org
In-Reply-To: <199605071412.XAA22794@genesis.atrad.adelaide.edu.au> from "Michael Smith" at May 7, 96 11:42:49 pm
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> Subject really says it all, however some more details would probably be
> helpful 8)
> 
> In all cases, I'm using 2.1-STABLE systems of a month or so ago as NFS
> servers.
> 
> Clients are all either the latest SNAP or more recent -current.
> 
> Not _all_ clients fail.  Of the tested systems, all the Pentiums work, and
> the 486 and 386 clients fail.  Failure symptoms are a total hang of all
> operations referencing a mounted filesystem.

On a hunch: try backing out the bcopy optimizations?


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.