From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Steven <steven@void.org>, nfs@lists.sourceforge.net
Subject: Re: Minor problem in nfsv3 write
Date: Tue, 20 Sep 2005 08:25:43 -0400 [thread overview]
Message-ID: <432FFFC7.7010803@redhat.com> (raw)
In-Reply-To: <20050920012525.GA26729@fieldses.org>
J. Bruce Fields wrote:
>On Mon, Sep 19, 2005 at 06:10:46PM -0700, Steven wrote:
>
>
>>There is a minor bug in the way writes are handled in nfs3. If the
>>client requests a write for more than 32k of data the server will only
>>write 32k but report that it wrote the whole amount.
>>
>>
>
>Our server also reports 32k as the maximum write size. So the bug is on
>the client side here, isn't it?
>
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.
Thanx...
ps
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-09-20 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 1:10 Minor problem in nfsv3 write Steven
2005-09-20 1:25 ` J. Bruce Fields
2005-09-20 12:25 ` Peter Staubach [this message]
2005-09-20 18:30 ` Steven
2005-09-20 19:26 ` J. Bruce Fields
2005-09-20 22:19 ` [PATCH] " Steven
2005-09-20 23:46 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2005-09-20 6:29 Sumeet Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=432FFFC7.7010803@redhat.com \
--to=staubach@redhat.com \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=steven@void.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.