[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <9FB1C80C-CF8A-4650-8918-475A19F353EB@redhat.com>
Date: Tue, 05 Mar 2024 06:39:25 -0500
From: Benjamin Coddington <bcodding@...hat.com>
To: Christian Theune <ct@...ingcircus.io>
Cc: Chuck Lever <chuck.lever@...cle.com>, linux-nfs@...r.kernel.org,
jlayton@...nel.org, linux-kernel@...r.kernel.org,
Linux regressions mailing list <regressions@...ts.linux.dev>,
trondmy@...merspace.com, anna@...nel.org
Subject: Re: nfs4_schedule_state_manager stuck in tight loop
On 5 Mar 2024, at 1:09, Christian Theune wrote:
> Hi,
>
> not sure whether I may have missed a response that didn’t make it back to me or any of the lists.
>
> Just in case, because the CC didn’t include the original addendum I made to my report:
>
> Addendum:
>
> I’ve checked kernel changelogs since then but didn’t find anything that I could relate to this aside from *maybe* dfda2a5eb66a685aa6d0b81c0cef1cf8bfe0b3c4 (rename(): fix the locking of subdirectories) which mentions NFS but doesn’t describe the potential impact.
>
> We’re running 5.15.148 now and as it’s been another 2 months there might be the chance of another lockup in the near future ;)
>
> If anyone has ideas on how to debug/approach a reproducer I’d be more than happy to help and try to provide more data.
>
> Cheers,
> Christian
When the problem occurs, use the
nfs4:nfs4_state_mgr
nfs4:nfs4_state_mgr_failed
tracepoints to see what the state manager might be doing.
Also a network capture might show what the state manager thread is up to if
it is sending operations.
Ben
Powered by blists - more mailing lists