I meant to say 3.10.0-229. Mixing my RHEL6 and RHEL7 prefixes... On Fri, May 29, 2015 at 12:51 PM, Olga Kornievskaia <aglo@xxxxxxxxx> wrote: > On Fri, May 29, 2015 at 9:44 AM, Benjamin Coddington > <bcodding@xxxxxxxxxx> wrote: >> On Thu, 7 May 2015, Olga Kornievskaia wrote: >> >>> Hi folks, >>> >>> Problem: >>> The upstream nfs4.0 client has problem where it will go into an >>> infinite loop of re-sending an OPEN when it's trying to recover from >>> receiving a BAD_STATEID error on an IO operation such READ or WRITE. >>> >>> How to easily reproduce (by using fault injection): >>> 1. Do nfs4.0 mount to a server. >>> 2. Open a file such that the server gives you a write delegation. >>> 3. Do a write. Have a server return a BAD_STATEID. One way to do so is >>> by using a python proxy, nfs4proxy, and inject BAD_STATEID error on >>> WRITE. >>> 4. And off it goes with the loop. >> >> Hi Olga, >> >> I've been trying to reproduce it, and I'm frustratingly unable. It sounds >> fairly easy to produce.. What version of the client produces this? >> > > Hi Ben, > > Problem exists in the upstream kernels as well but we noticed the > problem on RHEL7.1 distro (RedHat's 2.6.32-229.el7 kernel I think). > >> 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
