> On Jan 30, 2021, at 3:52 AM, A. Duvnjak <avian@xxxxxxxxxxxxxxxx> wrote: > > Thanks Chuck, > > I have some tcp dumps for you, some are too large to send via email even when compressed (i.e. approx 100M). Funnily enough I found a folder that I couldnt browse at all in Kodi (it will just crash when entering it), so I have a dump of both the attempt at browsing the folder (obviously with 5.10.11), and browsing the folder successfully (with 5.10.11). > > kodi_folder_freaks.bin (2.3M) The client RST's its connections in frames 223 and 224 just after a successful NFS READ. There's no indication in the wire capture about why. > kodi_folder_works.bin (25M) > > Below are tcp dumps of Kodi streaming approx 15 seconds of video footage. First is with 5.10.11 where it is struggling to play. Second is playing successfully with 5.10.10. > > kodi_struggling.bin (110M) I see some duplicate TCP Acks, which suggests the problem might be at the network layer and not in the NFS server. =========================================================================== ONC-RPC Service Response Times - kodi_struggling.pcap: Index Procedure Calls Min SRT (s) Max SRT (s) Avg SRT (s) Sum SRT (s) --------------------------------------------------------------------------- NFS Version 3 ACCESS 4 1 0.000119 0.000119 0.000119 0.000119 GETATTR 1 6 0.000059 0.000139 0.000122 0.000734 LOOKUP 3 24 0.000057 0.000201 0.000125 0.002999 READ 6 112 0.000087 0.014444 0.007711 0.863614 NFS Version 3 --------------------------------------------------------------------------- I don't see any READ errors. Avg READ RTT is 7 milliseconds, Max is 14 milliseconds. The server seems to be responsive. > https://deathbytelevision.com/kodi_works.bin (98M) Even more duplicate Acks here. =========================================================================== ONC-RPC Service Response Times - kodi_works.pcap: Index Procedure Calls Min SRT (s) Max SRT (s) Avg SRT (s) Sum SRT (s) --------------------------------------------------------------------------- NFS Version 3 ACCESS 4 1 0.000073 0.000073 0.000073 0.000073 FSINFO 19 1 0.004495 0.004495 0.004495 0.004495 GETATTR 1 7 0.000063 0.004627 0.000769 0.005386 LOOKUP 3 28 0.000031 0.008314 0.000389 0.010904 NULL 0 1 0.000103 0.000103 0.000103 0.000103 READ 6 98 0.001370 0.084851 0.010576 1.036461 READDIRPLUS 17 1 0.014783 0.014783 0.014783 0.014783 NFS Version 3 --------------------------------------------------------------------------- Avg READ RTT is 10 milliseconds, Max is 85 milliseconds. The server is responsive, but /slower/ in this case. I don't see anything obviously wrong at the NFS level in the "struggling" or "freaking" cases. At this point my advice is: - Reach out to kodi.tv to see if they can provide any insight or diagnostic tips to help us drill into this further. - If you know how to do a git bisect, you could bisect your server kernel between v5.10.10 and v5.10.11, looking for the place where Kodi starts to complain. There are some TCP changes in there that could be relevant. -- Chuck Lever
