From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: bfields@fieldses.org, chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Lockd error message is unclear.
Date: Tue, 27 Apr 2021 21:03:11 +0200 [thread overview]
Message-ID: <20210427190311.cjjzeded7hl3fkew@BitWizard.nl> (raw)
Hi,
Two things.....
I got:
lockd: cannot monitor <client>
in the logfile and the client was terrily slow/not working at all.
everything pointed to a lockd problem...
In the end... it turns out that my rpc.statd stopped working. I had
to go and download the sources to figure this out... I would firstly
suggest to improve the error message to give others running into this
more hints as to where to look.
The erorr message on line 169 of lockd.c could read:
lockd: Error in the rpc to rpc.statd to monitor %s\n
Would it be an idea to print the res.status error code?
That said...
When this situation is going on, the client grinds to a halt, and
lockd seems "stuck" in D state. I tried killing or stracing it, to try
to clear the error, before I found out it is a kernel deamon...
When this failure happens, I get the impression that lockd keeps on
trying to be "of service", retrying operations that are bound to
fail. So maybe the error should be cached, and then immediately
handled instead of making the client grind to a halt. (it is the (one
second?) timeout in nsm_mon_unmon and the big backlog of requests that
result in the same call and timeout that frustrate the client... )
Roger.
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Delftechpark 11 2628 XJ Delft, The Netherlands. KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a is going up. -- Chris Hadfield about flying up the space shuttle.
next reply other threads:[~2021-04-27 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 19:03 Rogier Wolff [this message]
2021-04-27 19:34 ` Lockd error message is unclear J. Bruce Fields
2021-04-27 21:10 ` Rogier Wolff
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=20210427190311.cjjzeded7hl3fkew@BitWizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=bfields@fieldses.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.