From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Chuck Lever <chuck.lever@oracle.com>, Jeff Layton <jlayton@kernel.org>
Cc: linux-nfs@vger.kernel.org
Subject: NFSD: Unable to initialize client recovery tracking! (-110)
Date: Fri, 19 Apr 2024 18:50:47 +0200 [thread overview]
Message-ID: <aaeae060-2be0-4b9f-818c-1b7d87e41a5f@molgen.mpg.de> (raw)
Dear Linux folks,
Since at least Linux 6.8-rc6, Linux logs the warning below:
NFSD: Unable to initialize client recovery tracking! (-110)
I haven’t had time to bisect yet, so if you have an idea, that’d be great.
Kind regards,
Paul
next reply other threads:[~2024-04-19 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 16:50 Paul Menzel [this message]
2024-05-21 9:55 ` NFSD: Unable to initialize client recovery tracking! (-110) Paul Menzel
2024-05-21 10:01 ` Jeff Layton
2024-05-24 11:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-24 12:46 ` Jeff Layton
2024-05-24 16:09 ` Chuck Lever III
2024-05-29 12:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-05-29 13:13 ` Jeff Layton
2024-05-29 13:16 ` Chuck Lever III
2024-05-29 13:27 ` Paul Menzel
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=aaeae060-2be0-4b9f-818c-1b7d87e41a5f@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=chuck.lever@oracle.com \
--cc=jlayton@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).