Re: NFSD threads hang when destroying a session or client ID

[Baptiste PELLEGRIN via Bugspray Bot <bugbot@kernel.org>]

Baptiste PELLEGRIN writes via Kernel.org Bugzilla:

Hello.

My clients are all v4.2 using Debian stable kernel 6.1.0-29-amd64 (= 6.1.123-1).

If you suspect one of my client doing "wrong things" checking my server trace. Give me the IP and I can give you back the client syslog.

In my case, one point seems important. The hang occur almost exactly one time per week. But not always the same day in the week (depending on when I reboot the server). The greater is the server uptime, the greater is the probability to see some "unrecognized reply" messages in syslog.

I always see one or two "unrecognized reply" message around 120 seconds before the hang message.

So it may something that happen on client or server weekly jobs ?
Or maybe some memory leak or cache corruption ?
Or something related to expired Kerberos cache file ?
Or expired NFS session ?
...

It seems also that the number of nfsd_cb_recall_any callback message increase with the server uptime. This seems in favor of the memory leak hypothesis.

Regards,

Baptiste.

View: https://bugzilla.kernel.org/show_bug.cgi?id=219710#c8
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)