From owner-freebsd-current  Mon Aug 11 11:11:16 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA20244
          for current-outgoing; Mon, 11 Aug 1997 11:11:16 -0700 (PDT)
Received: from lamb.sas.com (uucp@lamb.sas.com [192.35.83.8])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA20215
          for <freebsd-current@freebsd.org>; Mon, 11 Aug 1997 11:11:09 -0700 (PDT)
Received: from mozart by lamb.sas.com (5.65c/SAS/Gateway/01-23-95)
	id AA19529; Mon, 11 Aug 1997 14:11:01 -0400
Received: from iluvatar.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90)
	id AA00815; Mon, 11 Aug 1997 14:10:52 -0400
From: "John W. DeBoskey" <jwd@unx.sas.com>
Received: by iluvatar.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93)
	id AA02182; Mon, 11 Aug 1997 14:10:52 -0400
Message-Id: <199708111810.AA02182@iluvatar.unx.sas.com>
Subject: nfs v3 & network appliance
To: freebsd-current@freebsd.org
Date: Mon, 11 Aug 1997 14:10:51 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

   I have a copy of the latest snap up and running. Using nfs to 
access our v2 nfs servers works like a champ. However, trying to
access a network appliance nfs fileserver which speaks v3 locks
up tight.

   Does anyone have any ideas (or comments) that I might try? Has
anyone actually used -current against a netapp fileserver?

Thanks,
John

ps: No, this is NOT an SMP system.. :-)   It does, however, do the
    exact same thing under smp.
-- 
jwd@unx.sas.com       (w) John W. De Boskey          (919) 677-8000 x6915