Subject: Re: lockd: couldn't create RPC handle for (host)
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
In-Reply-To: <20051216205536.GA20497@tau.solarneutrino.net>
References: <20051216205536.GA20497@tau.solarneutrino.net>
Content-Type: text/plain
Date: Fri, 16 Dec 2005 18:49:05 -0500
Message-Id: <1134776945.7952.4.camel@lade.trondhjem.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 887
Lines: 26

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/