Date: Thu, 2 Nov 2006 16:52:07 -0500 From: John Baldwin <jhb@freebsd.org> To: "Julian H. Stacey" <jhs@flat.berklix.net> Cc: freebsd-hackers@freebsd.org, jhs@berlix.com Subject: Re: NFS on 6.1 limits at 4 Gig Message-ID: <200611021652.07853.jhb@freebsd.org> In-Reply-To: <200611022010.kA2KA9O7004585@fire.jhs.private> References: <200611021050.kA2AoH5S028916@fire.jhs.private> <200611021202.28351.jhb@freebsd.org> <200611022010.kA2KA9O7004585@fire.jhs.private>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday 02 November 2006 15:10, Julian H. Stacey wrote:
> John Baldwin wrote:
> > On Thursday 02 November 2006 05:50, Julian Stacey wrote:
> > > NFS fails on files >= 4 Gig Can someone confirm please.
> > >
> > > uname -r # 6.1-RELEASE (both hosts)
> > > # echo "1024 1024 * 4 * 1 + p" | dc # 4194305
> > > dd if=/dev/zero of=junk bs=1k count=4194305
> > > ls -l junk # 4294968320 bytes
> > > rsh an_nfs_host ls -l /host/`hostname -s`/usr/tmp/junk # 1024 byte size!
> > > # with count=4194304, ls shows 0 bytes.
> > >
> > > It's not AMD failing, but NFS, as with an /etc/amd.map with a
> > > non NFS entry for my host "laps" for efficiency (in case some
> > > shell on host laps mounts itself), the full size 4294968320 is seen.
> > > /etc/amd.map
> > > /defaults type:=host;fs:=${autodir}/${rhost};rhost:=${key}
> > > laps type:=link;fs:=..
> > >
> > > It's not just ls, cmp fails too, ( as also does my
> > > http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/cmpd.c )
> > > cmp -z junk /host/laps/usr/tmp/junk # junk /host/laps/usr/tmp/junk differ: size
> > >
> > > Is send-pr appropriate ?
> >
> > Are you using NFS v2 or v3? v2 doesn't support large files.
> >
> > John Baldwin
>
> Thanks, I don't know ! Whatever 6.1-RELEASE comes standard with.
>
> After your mail I did cd /usr/ports ; echo */*nfs*
> net-mgmt/nfsen net/nfsshell net/pcnfsd net/unfs3
> /usr/ports/net/unfs3 offers a non ernel V3 server
> but I'd still need a v3 client I suppose ?
> Are 6.2-pre or current using V3 NFS then ?
> Hints which way to jump / where to RTFM please :-)
It should default to v3, the nfs client in the base system can do either
v2 or v3. I'm not sure if amd is going to default to v2 with your map
file though. You can use tcpdump on the port with NFS traffic to see
if it's v2 or v3 though.
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200611021652.07853.jhb>