[pnfs] pnfs-client-temporary-patch-do-not-replay

[William A. (Andy) Adamson]

On 10/22/07, Benny Halevy <bhalevy at panasas.com> wrote:
>
> Hi Andy,
>
> when doing some removes in parallel from 8 clients
> I'm seeing the following message repeated endlessly:


are the clients endlessly sending replays of the removes?

the server does not have a sessions replay cache implemetation, so whatever
we do is a hack until we have an implementation. what is supposed to happen
is that the server will note the replay, and return the cached RPC from the
session cache.

commit 73953ace1a7472a5adadd56d6f564c5281a41b9c changes the server behaviour
from one hack to another (!) -  instead of a replayed sequence number on a
slot  returning NFS4ERR_BAD_SESSION on the OP_SEQUENCE it now returns
NFS_OK. this in turn lets the server continue processing the compound and
re-do the RPC instead of replay the cached rpc.

but the client is not supposed to send retry's of a request..
perhaps what is happening is that the client is not waiting for a reply
before using the slot for another request (the replay???)

do you have more information on the clients behaviour?


-->Andy


check_slot_seqid error. seqid N slot->sl_seqid N
>
> This message comes from commit 73953ace1a7472a5adadd56d6f564c5281a41b9c
>
> Please advise,
>
> Benny
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20071022/c66e08c6/attachment.htm