Bug#934160: Bug#962254: NFS(v4) broken at 4.19.118-2

[Elliott Mitchell <ehem+debian@m5p.com>]

I've run into a problem which produces the same behavior as bug #934160,
but attributed it elsewhere due to other observations.

What are the version(s) of the Linux kernel being used on your server and
clients?

I've confirmed using a 4.9 kernel on a client instead of a 4.19 kernel
also works around this issue.  In fact one client using a kernel from
4.19.98+1+deb10u1 source doesn't display the issue, but one using
4.19.118+2 source does.

This timeframe though doesn't match when you reported the issue.  Could
be there are several things working together to cause this.

I haven't yet tried tried using NFS version 4.1, instead of 4.2.


-- 
(\___(\___(\______          --=> 8-) EHM <=--          ______/)___/)___/)
 \BS (    |         ehem+sigmsg@m5p.com  PGP 87145445         |    )   /
  \_CS\   |  _____  -O #include <stddisclaimer.h> O-   _____  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445