At 09:36 AM 10/17/2008, Trond Myklebust wrote: >On Fri, 2008-10-17 at 09:32 -0400, Talpey, Thomas wrote: >> The fix here is to break the connection before retrying, a long-standing >> pet peeve of mine that NFSv3 historically does not do. > >It's not a perfect fix, which is why we haven't done that for NFSv3. > >When you break the connection, there is the chance that a reply to a >non-idempotent request may get lost, and that the server doesn't >recognise the retransmission due to the above mentioned imperfections >with the replay cache. In that case, the client may get a downright >_wrong_ reply (for instance, it may see an EEXIST reply to a mkdir >request that was actually successful). Well, the NFSv4 client will suffer the same issue in the above case. So, it's choose your poison. The antidote is to adopt NFSv4.1 asap. ;-) Sorry about the crossing replies btw. My own transmission was scheduled before pulling email to look for other replies! Hmm... Tom. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
