From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: lockd: couldn't create RPC handle for (host)
Date: Fri, 16 Dec 2005 18:49:05 -0500 [thread overview]
Message-ID: <1134776945.7952.4.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20051216205536.GA20497@tau.solarneutrino.net>
On Fri, 2005-12-16 at 15:55 -0500, Ryan Richter wrote:
> Hi, nfs locking stopped working on my file server running 2.6.15-rc5
> today. All clients that try locking operations hang, and I get the
> message from the server:
>
> lockd: couldn't create RPC handle for w.x.y.z
Points either to a client which is not responding to callbacks, or an
OOM situation on the server.
Does 'rpcinfo -u w.x.y.z 100021' work from the server?
> Also, the lockd process is unkillable, it looks like I'll have to
> reboot.
lockd cannot be killed as long as you have active nfsd threads or active
nfs client partitions. That is by design.
Cheers,
Trond
next prev parent reply other threads:[~2005-12-16 23:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 20:55 Ryan Richter
2005-12-16 23:49 ` Trond Myklebust [this message]
2005-12-16 23:58 ` Ryan Richter
2005-12-17 5:32 ` Trond Myklebust
2005-12-17 5:59 ` Ryan Richter
2005-12-17 6:43 ` Trond Myklebust
2005-12-17 7:02 ` Ryan Richter
2005-12-17 19:28 ` Trond Myklebust
2005-12-17 19:45 ` Ryan Richter
2005-12-18 8:33 ` Trond Myklebust
2005-12-18 18:01 ` Ryan Richter
2005-12-18 19:31 ` Trond Myklebust
2005-12-18 20:00 ` Ryan Richter
2005-12-18 22:24 ` Trond Myklebust
2005-12-18 22:44 ` Ryan Richter
2006-01-03 19:01 ` Ryan Richter
2006-01-18 0:02 ` Ryan Richter
2006-02-27 20:37 ` Ryan Richter
2005-12-19 18:49 ` [NFS] " Dan Stromberg
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=1134776945.7952.4.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=ryan@tau.solarneutrino.net \
/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
all inboxes | Powered by JetHome®