Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!killer!mit-eddie!uw-beaver!cornell!siegel
From: siegel@magni.cs.cornell.edu (Alexander Siegel)
Newsgroups: comp.protocols.nfs
Subject: Re: NFS "null block" bug encountered + FIX
Keywords: NFS null zero
Message-ID: <21628@cornell.UUCP>
Date: 9 Oct 88 20:15:59 GMT
References: <7376@bloom-beacon.MIT.EDU>
Sender: nobody@cornell.UUCP
Reply-To: siegel@cs.cornell.edu (Alexander Siegel)
Organization: Cornell Univ. CS Dept, Ithaca NY
Lines: 17

In article <7376@bloom-beacon.MIT.EDU> jtkohl@athena.mit.edu (John T Kohl) writes:
>At MIT Project Athena, we have been bitten hard by a problem in the 3.0
>(and 3.2) NFSSRC (VAX and IBM/RT 4.3BSD UNIX) handling of non-idempotent
...
>The fix we have implemented at Project Athena is a protocol revision,
...
>Our fix is to send the last known modification time in the truncation
>request to the NFS server.  When the server sees a truncation request

This is just a simple serialization protocol.  Why not just use
TCP for transmission instead of UDP?



Alex Siegel - CS graduate drudge at Cornell
a.k.a. Scimitar;  a.k.a. Phineas Ginn (SCA);  a.k.a. Trash
siegel@cs.cornell.edu   (607)255-1165