From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Anna Langley <jal58@cam.ac.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: PROBLEM: slow NFS locking "lockd: failed to monitor xxxxx"
Date: Thu, 26 Jul 2007 13:17:44 -0400 [thread overview]
Message-ID: <1185470264.6585.242.camel@localhost> (raw)
In-Reply-To: <46A8C058.40709@cam.ac.uk>
On Thu, 2007-07-26 at 16:40 +0100, Anna Langley wrote:
> [1] slow NFS locking, dmesg reports "lockd: failed to monitor xxxxx"
Which tells you that rpc.statd either isn't running, or isn't able to
receive RPC calls. Note that rpc.statd has to run on both the client and
the server.
> [2] Applications which set locks in NFS mounted home directories start
> very slowly.
>
> dmesg shows the following, repeated over and over:
>
> lockd: cannot monitor cabinet
> lockd: failed to monitor cabinet
See above. You need to fix your rpc.statd.
Trond
prev parent reply other threads:[~2007-07-26 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 15:40 PROBLEM: slow NFS locking "lockd: failed to monitor xxxxx" Anna Langley
2007-07-26 17:17 ` Trond Myklebust [this message]
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=1185470264.6585.242.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=jal58@cam.ac.uk \
--cc=linux-fsdevel@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 NNTP newsgroup(s).