mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Christian Theune <ct@flyingcircus.io>
Cc: 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: Fri, 23 Feb 2024 09:33:22 -0500	[thread overview]
Message-ID: <ZdisssP88_9o0BXn@manet.1015granger.net> (raw)
In-Reply-To: <8B04DA70-ABEF-44A4-BBA7-60968E6CFA10@flyingcircus.io>

On Fri, Feb 23, 2024 at 02:59:49PM +0100, Christian Theune wrote:
> Hi,
> 
> unfortunately I’m a bit light on details, but willing to provide better diagnostics as this moves along.
> 
> We’ve had two instances of NFS clients getting stuck with a kernel thread spinning around `nfs4_schedule_state_manager` AFAICT:
> 
> The first instance of this was last September on a Qemu VM running a 6.1.45 guest:
> 
> root 315344 44.5 0.0 0 0 ? D Sep05 781:38 \_ [172.22.56.83-manager]
> 
> It happened a second time in last December on another VM that was likely running 5.15.139. (We downgraded our fleet due to other stability issues from 6.1 to 5.15 in between those two incidents.)
> 
> My colleagues told me that no issues were visible in the logs at that time, the systems were generally usable but interacting with anything on NFS was (obviously) stuck. So apparently no (soft-) lock ups and no stalls were recorded, but I’ll ask my colleagues to either alert me or provide all of the logging they can get the next time this happens.
> 
> Cheers,
> Christian
> 
> PS: I’ve also recorded this in https://bugzilla.kernel.org/show_bug.cgi?id=217877 but switching to mail-based workflow now.

nfs4_schedule_state_manager() is part of the Linux NFS client, so
Cc'ing the client maintainers.

-- 
Chuck Lever

  parent reply	other threads:[~2024-02-23 14:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 13:59 Christian Theune
2024-02-23 14:08 ` Christian Theune
2024-02-23 14:33 ` Chuck Lever [this message]
2024-03-05  6:09   ` Christian Theune
2024-03-05 11:39     ` Benjamin Coddington

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=ZdisssP88_9o0BXn@manet.1015granger.net \
    --to=chuck.lever@oracle.com \
    --cc=anna@kernel.org \
    --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

all inboxes | Powered by JetHome®