From owner-freebsd-isp Thu Sep 30 3:24:56 1999 Delivered-To: freebsd-isp@freebsd.org Received: from relay04.indigo.ie (relay04.indigo.ie [194.125.133.228]) by hub.freebsd.org (Postfix) with SMTP id 970FB14F57 for ; Thu, 30 Sep 1999 03:24:52 -0700 (PDT) (envelope-from judgea@indigo.ie) Received: (qmail 5214 messnum 46469 invoked from network[194.125.133.235/relay-mgr.indigo.ie]); 30 Sep 1999 10:24:51 -0000 Received: from relay-mgr.indigo.ie (HELO indigo.ie) (194.125.133.235) by relay04.indigo.ie (qp 5214) with SMTP; 30 Sep 1999 10:24:51 -0000 To: Arjan van der Oest Cc: freebsd-isp@freebsd.org Subject: Re: NetApp NFS & FreeBSD In-reply-to: Message from Arjan van der Oest dated Wednesday at 17:43. From: Alan Judge Date: Thu, 30 Sep 1999 11:24:51 +0100 Message-Id: <19990930102453.970FB14F57@hub.freebsd.org> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Arjan> Is there anyone out there that uses this combination ? I've Arjan> heard rumours that due to some problems either with FreeBSD or Arjan> ONTAP this combination was not very reliable or didn't work at Arjan> all. NetApp was unsure... We've been doing this for virtually all of our production systems (we're a large ISP) for almost 2 years. email (qmail), apache, news, .... All using V3/UDP NFS. Versions of FreeBSD mainly 2.2.5/2.2.6 and 3.3. Ontap most versions, currently mostly 5.3.2 in a cluster. Works great and we've never had NFS related problems. One caveat, FreeBSD doesn't support NFS file locking as a client (does as a server, I think). That said, we don't need/use it and you could easily argue that NFS file locking is broken as designed. -- Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message