From: Steven <steven@void.org>
Subject: Re: Minor problem in nfsv3 write
Date: Tue, 20 Sep 2005 11:30:54 -0700
Message-ID: <20050920183054.BCB62F4@dead.void.org>
References: <20050920011046.23A07F4@dead.void.org> <20050920012525.GA26729@fieldses.org>  <432FFFC7.7010803@redhat.com>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Steven <steven@void.org>, nfs@lists.sourceforge.net
To: Peter Staubach <staubach@redhat.com>
In-Reply-To: Message from Peter Staubach <staubach@redhat.com>
   of "Tue, 20 Sep 2005 08:25:43 EDT." <432FFFC7.7010803@redhat.com>
Sender: nfs-admin@lists.sourceforge.net
Errors-To: nfs-admin@lists.sourceforge.net

> This would be a bug in the client, but if the server is going to attempt
> to write some of the data anyway, then it should correctly report the
> number of bytes written.  Otherwise, the server should reject the entire
> request.

I agree.  I don't think it is a good policy to tell the client that all
of the data was written when some was not.

For what it's worth, the RFC says that if the write size exceeds wtmax
then the server may write only wtmax bytes of the request.

--Steven


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs