Date: Thu, 25 Jan 2001 09:10:03 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Dan Nelson <dnelson@emsphone.com> Cc: current@FreeBSD.ORG Subject: Re: > 4GB with NFS? Message-ID: <Pine.BSF.4.21.0101250907270.13858-100000@beppo.feral.com> In-Reply-To: <20010125110438.A23179@dan.emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 25 Jan 2001, Dan Nelson wrote: > In the last episode (Jan 25), Matthew Jacob said: > > I came across an embarrassing comparison last night- > > > > FreeBSD NFS clients (well, i386) stop writing files at 4GB. > > > > Solaris, with O_LARGEFILE options in the open arguments, does not. > > > > Does anyone here know what FreeBSD ought to be doing about this? Or > > have I missed something? There is no O_LARGEFILE in fcntl.h (it is > > present for Solaris, ConvexOS and some other platforms, I believe). I > > thought the *BSDs had > 32 bit file support? Or is it only for local > > filesystems? > > FreeBSD has 64-bit file offsets by default, which make -DLARGEFILE > hackery unnecessary. So I thought! > > 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101250907270.13858-100000>