From owner-freebsd-current Thu Jan 25 9: 5: 8 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 2753D37B404 for ; Thu, 25 Jan 2001 09:04:48 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id f0PH4dK21538; Thu, 25 Jan 2001 11:04:39 -0600 (CST) (envelope-from dan) Date: Thu, 25 Jan 2001 11:04:38 -0600 From: Dan Nelson To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: > 4GB with NFS? Message-ID: <20010125110438.A23179@dan.emsphone.com> References: 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 08:45:10 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: > 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