From: Mike Galbraith <efault@gmx.de>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: regression: nfs mount (even idle) eventually hangs server
Date: Thu, 22 Dec 2022 05:44:25 +0100 [thread overview]
Message-ID: <36902a3dd6ee1a8656548ff5b5eadb88245e2799.camel@gmx.de> (raw)
In-Reply-To: <1A404CDB-95A8-4D04-B76B-91D4F063B489@oracle.com>
On Thu, 2022-12-22 at 04:28 +0000, Chuck Lever III wrote:
>
> Hi Mike-
Greetings,
> I'm guessing your client mounts with NFSv4.x.
Yes, mount says vers=4.2.
> We've been chasing a similar problem for a few months, but for
> lack of a solid reproducer, it has remained elusive.
>
> We believe the problem was introduced between 5.19 and 6.0. If
> you have a fairly reliable way to trigger the server hang, then
> maybe a bisect would be possible?
The 'solid' reproducer attribute is a bit of a problem, why I was
taking potshots at it. I'll try to sneak up on it.
-Mike
next prev parent reply other threads:[~2022-12-22 4:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <65ed34338c69cb034295f2c9cbe0af684d65d30f.camel@gmx.de>
2022-12-21 9:56 ` regression: nfs mount (even idle) eventually hangs server Mike Galbraith
2022-12-22 3:42 ` Mike Galbraith
2022-12-22 4:14 ` Mike Galbraith
2022-12-22 4:28 ` Chuck Lever III
2022-12-22 4:44 ` Mike Galbraith [this message]
2022-12-22 13:30 ` Mike Galbraith
2022-12-22 14:21 ` Chuck Lever III
2022-12-23 4:41 ` Mike Galbraith
2022-12-23 6:28 ` Mike Galbraith
2022-12-23 12:02 ` dai.ngo
2022-12-23 13:05 ` Mike Galbraith
2023-01-09 0:50 ` dai.ngo
2023-01-09 2:41 ` Mike Galbraith
2023-01-09 6:34 ` dai.ngo
2023-01-05 14:14 ` summary: " Mike Galbraith
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=36902a3dd6ee1a8656548ff5b5eadb88245e2799.camel@gmx.de \
--to=efault@gmx.de \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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