Return-Path: Date: Fri, 8 May 2015 15:00:48 +0200 (CEST) From: "Mkrtchyan, Tigran" To: Benjamin Coddington Cc: Olga Kornievskaia , Trond Myklebust , linux-nfs Message-ID: <752919938.1601268.1431090048609.JavaMail.zimbra@desy.de> In-Reply-To: References: <110354172.1516782.1431074928783.JavaMail.zimbra@desy.de> Subject: Re: 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 List-ID: Hi Ben, probably you can simulate, as Olga has suggested, with fault injection. I can I can prepare a snadalone version of your server, which returns BAD_STATEID on any IO request. Tigran. ----- Original Message ----- > From: "Benjamin Coddington" > To: "Mkrtchyan, Tigran" > Cc: "Olga Kornievskaia" , "Trond Myklebust" , "linux-nfs" > > Sent: Friday, May 8, 2015 2:25:19 PM > Subject: Re: 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID > On Fri, 8 May 2015, Mkrtchyan, Tigran wrote: > >> Hi Olga, >> >> I believe we see the same infinite loop without delegation with RHEL6/7 >> kernels, but without delegation being involved. Currently, on the server >> side, if client looping is detected, we return RESOURCE. This breaks the >> loop and application gets an IO error. >> >> Your fix is only covers the delegation case isn't it? >> >> Tigran. > > Tigran, do you have a BZ or can you tell me how to reproduce this? > > Ben > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html