From owner-freebsd-current Thu Jan 25 9:31:25 2001 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C357737B699 for ; Thu, 25 Jan 2001 09:31:07 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f0PHV4i22215; Thu, 25 Jan 2001 09:31:04 -0800 (PST) Date: Thu, 25 Jan 2001 09:31:04 -0800 From: Alfred Perlstein To: Matthew Jacob Cc: Dan Nelson , current@FreeBSD.ORG Subject: Re: > 4GB with NFS? Message-ID: <20010125093104.L26076@fw.wintelcom.net> References: <20010125111322.B23179@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from mjacob@feral.com on Thu, Jan 25, 2001 at 09:17:57AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Jacob [010125 09:18] wrote: > > > On Thu, 25 Jan 2001, Dan Nelson wrote: > > > 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? > > None. As in EOF. > > > Also, what > > version of FreeBSD are you using? > > 4.2 in this case. 1.5.1 for NetBSD. > > > Okay- I think from what you've said and what Thor said for NetBSD is that this > is "supposed to work!" (which accords with what *I* thought too). I'll do some > more debugging as I can (I'm in a project deadline for 3 projects this week). > > But I won't let it go! I was hoping to replace my Solaris box with either > FreeBSD or NetBSD as my main home directory server. FreeBSD 4.2 panics part > way through the first LADDIS runs I was using to test it with and I can't get > NetBSD to start as a LADDIS client (I hadn't got the auth sorted out yet), so > I've been trying to scrutinize a lot of things very closely in this area. This is an old problem that I think was never addressed. It has to do with the vm system (on i386). It may be fixed now, so keep playing a bit, if not open a problem report and someone ought to get to it. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message