From owner-freebsd-current Fri Oct 30 02:21:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14604 for freebsd-current-outgoing; Fri, 30 Oct 1998 02:21:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14585 for ; Fri, 30 Oct 1998 02:21:38 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA09006; Fri, 30 Oct 1998 21:21:25 +1100 Date: Fri, 30 Oct 1998 21:21:25 +1100 From: Bruce Evans Message-Id: <199810301021.VAA09006@godzilla.zeta.org.au> To: bright@hotjobs.com, current@FreeBSD.ORG Subject: Re: NFS broken with large files Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i have /com nfs mounted: >from fstab: >xxx:/com /com nfs rw,tcp,bg,nfsv3 0 0 > >ii'm trying to manipulate this file: >/com/bkup % ls -l www1-local.tar >-rw-r--r-- 1 root wheel 2162790400 Oct 27 21:56 www1-local.tar >... >I thought NFSv3 provided for very large file support? >not only that, this file is not _that_ large... just 2gigs. Only in theory. Known bugs include gratuitous truncation of the file size to u_long: nfs/nfs_bio.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_subs.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_subs.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)vap->va_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)np->n_size); nfs/nfs_vnops.c: vnode_pager_setsize(vp, (u_long)np->n_size); The casts are K&R support for the 4.4Lite vnode_pager_setsize() which doesn't only supports u_long sizes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message