From owner-freebsd-current Mon Aug 11 23:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02529 for current-outgoing; Mon, 11 Aug 1997 23:05:14 -0700 (PDT) Received: from dog.farm.org ([209.1.236.251]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02519 for ; Mon, 11 Aug 1997 23:05:06 -0700 (PDT) Received: (from dk@localhost) by dog.farm.org (8.7.5/dk#3) id XAA09369; Mon, 11 Aug 1997 23:06:38 -0700 (PDT) Date: Mon, 11 Aug 1997 23:06:38 -0700 (PDT) From: Dmitry Kohmanyuk Message-Id: <199708120606.XAA09369@dog.farm.org> To: jwd@unx.sas.com (John W. DeBoskey) Cc: freebsd-current@freebsd.org Subject: Re: nfs v3 & network appliance Newsgroups: cs-monolit.gated.lists.freebsd.current Organization: FARM Computing Association Reply-To: dk+@ua.net X-Newsreader: TIN [version 1.2 PL2] Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <199708111810.AA02182@iluvatar.unx.sas.com> you wrote: > 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? I have used different vintages of 2.2 branch, and it stopped working around October (not very sure, but NFSv3 is broken in 2.2.1 and later; maybe it was fixed very recently). No idea about current, but I expect it to be in the same stage. The quick test is rm -rf big directory structure (like /sys tree). We run F330 with 4.1c (tried with several versions starting with 4.0 betas). Try disabling tcp mounts (if you enable them on a client); NetApp claim a bug in v3/TCP. -- "Now is the time for the quick brown fox to jump over the moon." - rblander@undergrad.math.uwaterloo.ca