>>>>> "CL" == Chuck Lever <chuck.lever@xxxxxxxxxx> writes: CL> The server is returning SEQ_MISORDERED to a singleton SEQUENCE. CL> That suggests the client is trying to re-establish its lease but is CL> sending a slot nr the server doesn't recognize for the virtual slot CL> used for this purpose. Could be a problem on either side, and I CL> don't know enough to say how this loop could have started. In case I didn't say so earlier, the server is just Centos 7.6 running that heavily modified 3.10.0-957.1.3.el7.x86_64. I was not able to reproduce anything like this throughout the 4.19 cycle but it started cropping up pretty quickly on user desktops after booting into 4.20.3 (the first of the 4.20 series I tried). And it does not reoccur after rebooting back to 4.19.15. Of course I know that doesn't absolve the server. It is possible for me to try to push a mainline kernel to all of the relevant file servers, but that obviously carries other overhead and risks that I would certainly prefer to avoid. I just wish I knew how to reproduce this other than sticking it on a bunch of machines and waiting until people complain. - J<
