From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: PROBLEM: slow NFS locking "lockd: failed to monitor xxxxx" Date: Thu, 26 Jul 2007 13:17:44 -0400 Message-ID: <1185470264.6585.242.camel@localhost> References: <46A8C058.40709@cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Anna Langley Return-path: Received: from pat.uio.no ([129.240.10.15]:39360 "EHLO pat.uio.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751567AbXGZRRr (ORCPT ); Thu, 26 Jul 2007 13:17:47 -0400 In-Reply-To: <46A8C058.40709@cam.ac.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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