From: Benjamin Coddington <bcodding@redhat.com>
To: Christian Theune <ct@flyingcircus.io>
Cc: Chuck Lever <chuck.lever@oracle.com>,
linux-nfs@vger.kernel.org, jlayton@kernel.org,
linux-kernel@vger.kernel.org,
Linux regressions mailing list <regressions@lists.linux.dev>,
trondmy@hammerspace.com, anna@kernel.org
Subject: Re: nfs4_schedule_state_manager stuck in tight loop
Date: Tue, 05 Mar 2024 06:39:25 -0500 [thread overview]
Message-ID: <9FB1C80C-CF8A-4650-8918-475A19F353EB@redhat.com> (raw)
In-Reply-To: <3404A3C2-31BE-4D39-A256-E3A1FB48ACFB@flyingcircus.io>
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
prev parent reply other threads:[~2024-03-05 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 13:59 nfs4_schedule_state_manager stuck in tight loop Christian Theune
2024-02-23 14:08 ` Christian Theune
2024-02-23 14:33 ` Chuck Lever
2024-03-05 6:09 ` Christian Theune
2024-03-05 11:39 ` Benjamin Coddington [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9FB1C80C-CF8A-4650-8918-475A19F353EB@redhat.com \
--to=bcodding@redhat.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=ct@flyingcircus.io \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=trondmy@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).