Re: PROBLEM: slow NFS locking "lockd: failed to monitor xxxxx"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux