From owner-freebsd-isp Mon Jan 4 14:01:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA11208 for freebsd-isp-outgoing; Mon, 4 Jan 1999 14:01:10 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA11203 for ; Mon, 4 Jan 1999 14:01:09 -0800 (PST) (envelope-from kstone@win.net) Received: from hendrix (hendrix.win.net [204.215.209.213]) by ns1.win.net (8.8.8/8.6.9) with SMTP id RAA26189 for ; Mon, 4 Jan 1999 17:00:33 -0500 (EST) Message-ID: <005e01be382d$9625dc60$d5d1d7cc@hendrix.win.net> From: "Kyle Stone" To: Subject: Problems with Network Appliances and FreeBSD's NFS3... Date: Mon, 4 Jan 1999 17:00:00 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We were experiencing a problem with NFS3 and our netapp server. After a few minutes into a "make world"... I'd get a complaint about null files in one of the source files. After investigating this I found pages of nulls in the middle of source code files that were on the netapp server. The nulls would disappear and reappear randomly after remounting the netapp server. We determined it was a problem in the nfs3 either on the FreeBSD side or on the netapps side. Either way it can be resolved by using this as an example in your /etc/fstab file... server:/directory /mount.point nfs rw, nfsv3, -r4096, -w4096 0 0 The -r and -w options is what makes it work with nfs version 3. Kyle Stone Unix Admin Win.Net http://www.win.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message