Re: guard on SETATTR

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Peter Staubach (Peter.Staubach@Sun.COM)
Date: 06/18/01-11:33:59 AM Z 

Message-Id: <200106181634.KAA26403@amon.Central.Sun.COM>
Date: Mon, 18 Jun 2001 10:33:59 -0600 (MDT)
From: Peter Staubach <Peter.Staubach@Sun.COM>
Subject: Re: guard on SETATTR


> 
> Does anybody know what happened to the guard
> mechanism for SETATTR that was in V3?  It isn't
> in V4 and I'm wondering why.
> 
> Is it the case that it has turned out to be
> useless (i.e. that no clients use it)?  It doesn't
> appear that it would be difficult for a server to 
> implement so even if it were used only by a few people, 
> it doesn't seem as though there would be a need to 
> remove it from NFS.
> 
> Anybody remember the history here?

The guard mechanism for SETATTR in NFS Version 3 is extremely useful.
It is used by most clients, at least, to protect requests which change
the size of the file.  These requests can cause data loss if a
retransmitted request is not caught properly and is reexecuted.

This sort of functionality is good at reducing the dependence on the
RPC duplicate request processing.

		ps

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-01:48:50 AM Z CST