From owner-freebsd-current  Sun Apr 21 02:02:24 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA10073
          for current-outgoing; Sun, 21 Apr 1996 02:02:24 -0700 (PDT)
Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA10067
          for <current@FreeBSD.ORG>; Sun, 21 Apr 1996 02:02:18 -0700 (PDT)
Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.6.12/8.6.12) id CAA26829; Sun, 21 Apr 1996 02:06:00 -0700
Date: Sun, 21 Apr 1996 02:06:00 -0700
Message-Id: <199604210906.CAA26829@sunrise.cs.berkeley.edu>
To: jkh@time.cdrom.com
CC: current@FreeBSD.ORG
In-reply-to: <245.829962579@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Anyone else notice NFS broken in -current?
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * Running the latest 2.2 kernels on two boxes here, I can only use NFS
 * for a short time before any process doing NFS I/O hangs.  After awhile
 * of this, one of the systems will then reset to the BIOS.
 * 
 * This and other reports now leads me to say that NFS is very, very
 * broken.  The only question is - who broke it, and when?

I don't see crashes (well I do (reported to -current awhile back) but
they are not NFS related) but I noticed that if I redirect the output
of a program to an NFS-mounted disk under heavy (local ccd) load, the
output gets mangled with the environment of the process.

If the output is redirected to a local file, it works fine.

Satoshi