Date: Thu, 25 Jan 2001 11:04:38 -0600 From: Dan Nelson <dnelson@emsphone.com> To: Matthew Jacob <mjacob@feral.com> Cc: current@FreeBSD.ORG Subject: Re: > 4GB with NFS? Message-ID: <20010125110438.A23179@dan.emsphone.com> In-Reply-To: <Pine.BSF.4.21.0101250841150.13858-100000@beppo.feral.com>; from "Matthew Jacob" on Thu Jan 25 08:45:10 GMT 2001 References: <Pine.BSF.4.21.0101250841150.13858-100000@beppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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. -- Dan Nelson dnelson@emsphone.com 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?20010125110438.A23179>