> -----Original Message----- > From: J. Bruce Fields [mailto:bfields@xxxxxxxxxxxx] > Sent: Saturday, October 29, 2011 8:15 PM > To: Myklebust, Trond > Cc: David Flynn; linux-nfs@xxxxxxxxxxxxxxx; Chuck Lever > Subject: Re: NFS4ERR_STALE_CLIENTID loop > > On Sat, Oct 29, 2011 at 07:29:36PM +0200, Trond Myklebust wrote: > > OK. This is the first time I've seen this tcpdump. > > > > The problem seems like a split-brain issue on the server... On the one > > hand, it is happily telling us that our lease is OK when we RENEW. > > Then when we try to use said lease in an OPEN, it is replying with > > STALE_CLIENTID. > > > > IOW: This isn't a problem I can fix on the client whether or not I add > > exponential backoff. The problem needs to be addressed on the server > > by the Solaris folks.... > > Is there any simple thing we could do on the client to reduce the impact of > these sorts of loops? WHY? Those loops aren't supposed to happen if the server works according to spec. > Given that we know there are bad servers out there it might be nice to do if > it's not complicated. Again WHY? We can't fix a broken server by backing off correctly formed requests. If a server wants us to back off, it will send us NFS4ERR_DELAY. > (Though as a server implementer my purely selfish impulse is to leave things > as they are since it ensures I'll get bug reports if I screw > up....) You would have gotten the same bugreport. That said, I refuse to change the client to accommodate buggy servers. The solution to the problem of buggy servers is to fix those servers. Trond -- 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
