From: Tom Talpey <tom@talpey.com>
To: "Benoît Gschwind" <benoit.gschwind@minesparis.psl.eu>,
"Chuck Lever III" <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfsd stuck in D (disk sleep) state
Date: Mon, 28 Oct 2024 13:38:03 -0400 [thread overview]
Message-ID: <181cdcf6-2cc2-4f71-92e1-8ac2ab3fbfb0@talpey.com> (raw)
In-Reply-To: <a4db98210dddb49b8810721b9c699a4d1c4915c1.camel@minesparis.psl.eu>
On 10/28/2024 1:01 PM, Benoît Gschwind wrote:
> Le lundi 28 octobre 2024 à 08:46 -0400, Tom Talpey a écrit :
>>
>> Was the client actually attempting to mount or unmount?
>
> The servers were running for a while, thus, as far as I know my setup,
> there is no ongoing mount or unmount. Moreover none of the clients were
> rebooting, starting or shutting down.
Interesting. I would therefore suspect the create_session was simply a
reconnect after some kind of transport connection error/loss, and the
destroy_session callers are hung for the same reason. And I agree with
Chuck that a network trace will help identify the patch which is needed
here.
You may have to let the trace run for a minute or two to detect all the
retry traffic between the client and server threads.
Tom.
next prev parent reply other threads:[~2024-10-28 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 19:27 nfsd stuck in D (disk sleep) state Benoît Gschwind
2024-10-23 19:38 ` Chuck Lever III
2024-10-24 8:07 ` Benoît Gschwind
2024-10-28 9:18 ` Benoît Gschwind
2024-10-28 12:46 ` Tom Talpey
2024-10-28 13:32 ` Chuck Lever III
2024-10-28 17:01 ` Benoît Gschwind
2024-10-28 17:38 ` Tom Talpey [this message]
2024-10-28 17:27 ` Jeff Layton
2024-10-29 13:49 ` Jeff Layton
2024-10-29 20:04 ` Jeff Layton
2025-01-20 9:22 ` Benoît Gschwind
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=181cdcf6-2cc2-4f71-92e1-8ac2ab3fbfb0@talpey.com \
--to=tom@talpey.com \
--cc=benoit.gschwind@minesparis.psl.eu \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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