diff options
| author | peter <peter@FreeBSD.org> | 1998-05-30 16:33:58 +0000 |
|---|---|---|
| committer | peter <peter@FreeBSD.org> | 1998-05-30 16:33:58 +0000 |
| commit | aa33f209931229b1ec794891bd3a69a8eff05835 (patch) | |
| tree | 5c600b7c603c70dd7c1f21b9426387f4c7902f04 /sys/nfsclient/nfsmount.h | |
| parent | 0d948cca0487b241fec6cc5211d55dc5ffabb72c (diff) | |
| download | FreeBSD-src-aa33f209931229b1ec794891bd3a69a8eff05835.zip FreeBSD-src-aa33f209931229b1ec794891bd3a69a8eff05835.tar.gz | |
When using NFSv3, use the remote server's idea of the maximum file size
rather than assuming 2^64. It may not like files that big. :-)
On the nfs server, calculate and report the max file size as the point
that the block numbers in the cache would turn negative.
(ie: 1099511627775 bytes (1TB)).
One of the things I'm worried about however, is that directory offsets
are really cookies on a NFSv3 server and can be rather large, especially
when/if the server generates the opaque directory cookies by using a local
filesystem offset in what comes out as the upper 32 bits of the 64 bit
cookie. (a server is free to do this, it could save byte swapping
depending on the native 64 bit byte order)
Obtained from: NetBSD
Diffstat (limited to 'sys/nfsclient/nfsmount.h')
| -rw-r--r-- | sys/nfsclient/nfsmount.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/sys/nfsclient/nfsmount.h b/sys/nfsclient/nfsmount.h index 2d502bd..ecb4f05 100644 --- a/sys/nfsclient/nfsmount.h +++ b/sys/nfsclient/nfsmount.h @@ -34,7 +34,7 @@ * SUCH DAMAGE. * * @(#)nfsmount.h 8.3 (Berkeley) 3/30/95 - * $Id: nfsmount.h,v 1.13 1997/08/16 19:16:05 wollman Exp $ + * $Id: nfsmount.h,v 1.14 1998/05/19 07:11:27 peter Exp $ */ @@ -92,6 +92,7 @@ struct nfsmount { short nm_bufqlen; /* number of buffers in queue */ short nm_bufqwant; /* process wants to add to the queue */ int nm_bufqiods; /* number of iods processing queue */ + u_int64_t nm_maxfilesize; /* maximum file size */ }; #if defined(KERNEL) || defined(_KERNEL) |
