From owner-freebsd-current  Fri May 24 14:20:32 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA29254
          for current-outgoing; Fri, 24 May 1996 14:20:32 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA29249
          for <current@freebsd.org>; Fri, 24 May 1996 14:20:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id OAA08703 for <current@freebsd.org>; Fri, 24 May 1996 14:20:11 -0700 (PDT)
To: current@freebsd.org
Subject: NFS over udp broken?
Date: Fri, 24 May 1996 14:20:11 -0700
Message-ID: <8701.832972811@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Try this:

Given:
	machine-a:/some/cvs/repository

Do:
	machine-b# mount_nfs -U machine-a:/some/cvs/repository /repo
	machine-b# setenv CVSROOT /repo
	machine-b# cvs co src

You'll get about 50 files into the checkout operation before machine-b
panics.

Now do:
	machine-b# mount_nfs -T machine-a:/some/cvs/repository /repo
	machine-b# setenv CVSROOT /repo
	machine-b# cvs co src

Using NFS over tcp instead of udp, the entire checkout operation succeeds.

Anyway, just some food for thought and perhaps known-problem #4381 in
-current's NFS.  Can anyone else reproduce?  This feature, at least,
sort of used to work. :-)

					Jordan