From: Emmanuel Florac <eflorac@intellique.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: nlockmgr freezing when using Ubuntu 13.04 (3.8 kernel) clients
Date: Thu, 17 Oct 2013 12:37:13 +0200 [thread overview]
Message-ID: <20131017123713.588319c2@harpe.intellique.com> (raw)
Hi list,
this is probably an Ubuntu bug, however it put two different servers in
the dumps, running different kernels so I send this in case it may help
someone.
Here is the sort of messages clogging the NFS servers logs:
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipntheo12
statd: server rpc.statd not responding, timed out
lockd: cannot unmonitor ipnnester13
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipngrid01.in2p3.fr
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
statd: server rpc.statd not responding, timed out
lockd: cannot monitor ipnweb2
lockd: server ipnweb2 not responding, timed out
lockd: server ipnweb2 not responding, timed out
There are about 80 NFS clients (home directories) on these. They worked
perfectly for years until 2 clients were upgraded to 13.04.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
reply other threads:[~2013-10-17 10:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131017123713.588319c2@harpe.intellique.com \
--to=eflorac@intellique.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;
as well as URLs for NNTP newsgroup(s).