Hi Tigran, I think you are hitting something else as mine is as you mentioned has to do with delegation. Also, RHEL6.6 code is very different from RHEL7.1 (or upstream). I haven't tested my test case on RHEL6.6 but just looking at it, I don't think it has the same OPEN loop problem. Ben, I didn't include this in my original message but we do have BZ open for the problem by Jorge Mora, Bug 1219184: Infinite OPEN loop on NFSv4.0 when I/O receives NFS4ERR_BAD_STATEID https://bugzilla.redhat.com/show_bug.cgi?id=1219184 On Fri, May 8, 2015 at 9:13 AM, Mkrtchyan, Tigran <tigran.mkrtchyan@xxxxxxx> wrote: > No, Olga's case includes delegation, which our server does not supports. > > Tigran. > > ----- Original Message ----- >> From: "Benjamin Coddington" <bcodding@xxxxxxxxxx> >> To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@xxxxxxx> >> Cc: "Olga Kornievskaia" <aglo@xxxxxxxxx>, "Trond Myklebust" <trond.myklebust@xxxxxxxxxxxxxxx>, "linux-nfs" >> <linux-nfs@xxxxxxxxxxxxxxx> >> Sent: Friday, May 8, 2015 3:08:03 PM >> Subject: Re: 4.0 NFS client in infinite loop in state recovery after getting BAD_STATEID > >> Yes, I've done that, and the client's behavior correctly cycles through >> OPEN, then READ with the new stateid. Are you able to create what Olga's >> talking about -- which is (I believe) a loop of just OPENs? >> >> Ben >> >> On Fri, 8 May 2015, Mkrtchyan, Tigran wrote: >> >>> 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" <bcodding@xxxxxxxxxx> >>> > To: "Mkrtchyan, Tigran" <tigran.mkrtchyan@xxxxxxx> >>> > Cc: "Olga Kornievskaia" <aglo@xxxxxxxxx>, "Trond Myklebust" >>> > <trond.myklebust@xxxxxxxxxxxxxxx>, "linux-nfs" >>> > <linux-nfs@xxxxxxxxxxxxxxx> >>> > 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@xxxxxxxxxxxxxxx >>> > More majordomo info at http://vger.kernel.org/majordomo-info.html >>> -- >>> 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 >> -- >> 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 -- 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
