From: Harald Dunkel <harald.dunkel@aixigo.com>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Calum Mackay <calum.mackay@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfsd becomes a zombie
Date: Wed, 3 Jul 2024 06:14:01 +0200 [thread overview]
Message-ID: <987ec8b2-40da-4745-95c2-8ffef061c66f@aixigo.com> (raw)
In-Reply-To: <91607B76-4A08-47A2-98CC-8DA10215CD69@oracle.com>
On 2024-07-02 20:17:11, Chuck Lever III wrote:
>
> Harald, none of this is any more probative than the first
> report you sent. We can't tell what's going on unless you
> can help us debug the problem. We're just not set up as a
> help desk. Have you contacted your Linux vendor and asked
> for help?
>
Understood. I highly appreciate your work on the NFS implementation.
Maybe it is not important, but did you notice that the most recent
"Got unrecognized reply" messages in dmesg did not show up in /var/\
log/kern.log, except for the first message immediately before NFS got
frozen? Usually both show the same.
Regards
Harri
next prev parent reply other threads:[~2024-07-03 4:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 6:55 nfsd becomes a zombie Harald Dunkel
2024-06-17 14:31 ` Chuck Lever III
2024-06-17 19:20 ` Calum Mackay
2024-06-18 14:29 ` Harald Dunkel
2024-06-18 14:32 ` Harald Dunkel
2024-06-18 14:52 ` Chuck Lever
2024-06-19 7:32 ` Harald Dunkel
2024-06-19 7:56 ` Harald Dunkel
2024-06-19 13:14 ` Chuck Lever III
2024-06-20 5:29 ` Harald Dunkel
2024-06-20 19:09 ` Chuck Lever III
2024-07-02 17:25 ` Harald Dunkel
2024-07-02 18:17 ` Chuck Lever III
2024-07-03 4:14 ` Harald Dunkel [this message]
2024-12-25 9:15 ` nfsd blocks indefinitely in nfsd4_destroy_session (was: Re: nfsd becomes a zombie) Salvatore Bonaccorso
2025-01-01 19:24 ` nfsd blocks indefinitely in nfsd4_destroy_session Chuck Lever
2025-01-07 21:17 ` Salvatore Bonaccorso
2025-01-08 13:33 ` Chuck Lever
2025-01-08 14:54 ` Christian Herzog
2025-01-08 15:07 ` Chuck Lever
2025-01-09 11:56 ` Christian Herzog
2025-01-09 12:42 ` Jeff Layton
2025-01-09 13:56 ` Chuck Lever
2025-01-09 16:32 ` Chuck Lever
[not found] ` <f0705a65549ef253.67823675@ac-grenoble.fr>
2025-01-16 20:07 ` Chuck Lever
2025-01-17 19:43 ` Baptiste PELLEGRIN
2025-01-17 20:27 ` Chuck Lever
2025-01-09 15:49 ` Chuck Lever
2025-01-09 15:58 ` Christian Herzog
2025-01-09 16:09 ` Chuck Lever
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=987ec8b2-40da-4745-95c2-8ffef061c66f@aixigo.com \
--to=harald.dunkel@aixigo.com \
--cc=calum.mackay@oracle.com \
--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