From: Chuck Lever <chuck.lever@oracle.com>
To: Harald Dunkel <harald.dunkel@aixigo.com>
Cc: Calum Mackay <calum.mackay@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: nfsd becomes a zombie
Date: Tue, 18 Jun 2024 10:52:00 -0400 [thread overview]
Message-ID: <ZnGfEDvQB1FRGVQK@tissot.1015granger.net> (raw)
In-Reply-To: <661a6c9a-81d6-46fd-87ec-274100b12189@aixigo.com>
On Tue, Jun 18, 2024 at 04:29:55PM +0200, Harald Dunkel wrote:
> On 2024-06-17 21:20:54, Calum Mackay wrote:
> >
> > Harald: do you have a Debian/Ubuntu kernel version that doesn't see the
> > issue, please? i.e. ideally from the same 6.1.y series…
> >
>
> I had migrated the Server from Debian 11 to Debian 12 on Dec 11th 2023.
> The kernel version provided by Debian 11 at that time was 5.10.197. I
> can't remember having seen a frozen nfsd with this version.
>
> Since Dec 11th I had these kernels in use (all provided by Debian):
>
> 6.1.66 linux-image-6.1.0-15-amd64
> 6.1.69 linux-image-6.1.0-17-amd64
> 6.1.76 linux-image-6.1.0-18-amd64
> 6.1.85 linux-image-6.1.0-20-amd64
> 6.1.90 linux-image-6.1.0-21-amd64
>
> These are all "upstream" version numbers. The second column lists
> Debian's package names.
>
> AFAIR nfsd got stuck only on the 6.1.90 kernel (installed and booted
> on May 18th, first time freeze on May 26th). But I've got a weak
> memory in cases like this. I haven't found older kernel log files.
>
> Please remember that I have seen a frozen nfsd only 3 times since
> May 26th. Its not easy to reproduce.
I can find no NFSD or SUNRPC changes between v6.1.85 and v6.1.90.
Between v6.1.76 and v6.1.85, there are 48 NFSD changes, 8 changes to
fs/nfs/, and 3 changes to net/sunrpc/.
Are there any NFS client changes during the second half of May that
correlate with the NFSD misbehavior?
--
Chuck Lever
next prev parent reply other threads:[~2024-06-18 14:52 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 [this message]
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
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=ZnGfEDvQB1FRGVQK@tissot.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=calum.mackay@oracle.com \
--cc=harald.dunkel@aixigo.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