From owner-freebsd-questions  Fri Feb 21 13:01:23 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA22893
          for questions-outgoing; Fri, 21 Feb 1997 13:01:23 -0800 (PST)
Received: from cs.rice.edu (cs.rice.edu [128.42.1.30])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22878
          for <questions@freebsd.org>; Fri, 21 Feb 1997 13:01:19 -0800 (PST)
Received: from acpc.cs.rice.edu (acpc.cs.rice.edu [128.42.1.67]) by cs.rice.edu (8.8.5/8.7.1) with ESMTP id PAA28065; Fri, 21 Feb 1997 15:01:16 -0600 (CST)
Received: from acpc.cs.rice.edu (localhost.cs.rice.edu [127.0.0.1]) by acpc.cs.rice.edu (8.8.5/8.7.3) with ESMTP id PAA00194; Fri, 21 Feb 1997 15:01:15 -0600 (CST)
Message-Id: <199702212101.PAA00194@acpc.cs.rice.edu>
To: questions@freebsd.org
cc: alc@cs.rice.edu
Subject: NFS & TCP
Date: Fri, 21 Feb 1997 15:01:15 -0600
From: Alan Cox <alc@cs.rice.edu>
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Has anyone been successful in using TCP as the transport for NFS
under version 2.2?  My server is a SparcStation running Solaris 2.5.
Attempting to generate a tar file of a directory tree on a file
system mounted with TCP as the transport reliably produces one
of three errors:

1. tar says: "Stale NFS handle"

2. tar says: "RPC struct is bad"

3. kernel crashes in fifo_badop called from getdirentries.

The latter is more common if the mount is using NFS v3, but
it also fails under v2.

Alan