[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Subtle NFS incompatibility with SunOS 4.1.1 on 68K
cmhanson%eschatologist.net@localhost (Chris Hanson) writes:
>So something is definitely going wrong in what the server is reporting under NFSv2 for a >2GB volume.
NFSv2 uses signed 32bit integers and the code simply truncates larger numbers.
There is no perfect solution since NFSv2 cannot handle larger filesytems or
files, but clamping the values to INT32_MAX should help. There are two
places that are relevant: filesystem data (size, free+avail blocks)
and file data (file length).
For files there is a danger. SunOS did fail syscalls for large files
and hid them from directory listings to prevent programs from using
clamped or otherwise truncated size values. For simple things, like
writing a logfile that grows beyond 2GB that's maybe too strong.
On the other hand, Your SunOS client may not yet support large files,
so it would be a good thing.
Michael van Elst
"A potential Snark may lurk in every tree."
Main Index |
Thread Index |