From owner-freebsd-current Thu Jan 25 9:13:43 2001 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id DC95D37B400 for ; Thu, 25 Jan 2001 09:13:25 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id f0PHDMD02053; Thu, 25 Jan 2001 11:13:22 -0600 (CST) (envelope-from dan) Date: Thu, 25 Jan 2001 11:13:22 -0600 From: Dan Nelson To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: > 4GB with NFS? Message-ID: <20010125111322.B23179@dan.emsphone.com> References: <20010125110438.A23179@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.13i In-Reply-To: ; from "Matthew Jacob" on Thu Jan 25 09:10:03 GMT 2001 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 25), Matthew Jacob said: > On Thu, 25 Jan 2001, Dan Nelson wrote: > > Make sure you're using NFSv3 mounts (should be the default, but if not, > > add "nfsv3" to the options column in fstab). I cross-mount FreeBSD, > > Tru64, and Solaris boxes via NFS and can access large files on all > > combinations of client and server. > > Huh. Interesting. The default showed up as a nfsv3 mount: > > 1/25 2:12 mountd/v3: granted 192.67.166.79 to /bob ro=0 uid0=60001 > > The solaris mount showed up as: > > 1/25 2:06 mountd/v3: granted 192.67.166.155 to /bob ro=0 uid0=60001 > 1/25 2:06 nfs/tcp accepted 192.67.166.155,1023 > > I'll try an explicit v3 mount/tcp and see if it's better. I use UDP mounts as it's easier to debug traces. The next step is to start looking as packet dumps... When you say that the FreeBSD clients "stop writing", what error do they get? Also, what version of FreeBSD are you using? -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message