From owner-freebsd-hackers  Wed May 15 05:54:53 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id FAA13866
          for hackers-outgoing; Wed, 15 May 1996 05:54:53 -0700 (PDT)
Received: from starfire.mn.org (root@starfire.skypoint.net [199.86.32.187])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA13859
          for <hackers@FreeBSD.org>; Wed, 15 May 1996 05:54:50 -0700 (PDT)
From: john@starfire.mn.org
Received: (from john@localhost)
	by starfire.mn.org (8.6.12/1.1)  id HAA10118
	for hackers@FreeBSD.org; Wed, 15 May 1996 07:59:05 -0500
Message-Id: <199605151259.HAA10118@starfire.mn.org>
Subject: NFS problems between FreeBSD 2.1.0-R(CD) server and Unixware 2.03 client
To: hackers@FreeBSD.org (FreeBSD hackers)
Date: Wed, 15 May 1996 07:59:04 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

We are getting file truncation (to multiples of 1024 bytes) and strange
errors (NFS write error 4, along with lots of hex info) in the log
files on the client, while the server doesn't report any problems.
We have rsize and wsize set to 1024.  I am running Andrew Gordon's stub
rpc.lockd and rpc.statd to keep things happy.

Can anyone help me?  This is in a production environment, and it is
really a Bad Thing.

Please respond directly, as I do not subscribe to this list.

		   John Lind, Starfire Consulting Services
E-mail: john@starfire.MN.ORG		USnail: PO Box 17247, Mpls MN  55417