On Sat, 2010-05-22 at 07:49 +0800, Steven Shiau wrote:
> Same problem here. However, mine is on the client side.
> On sid system, running kernel is 2.6.32-5-686, nfs-common is 1:1.2.2-1.
> When I mount my NFS server 192.168.120.254, it works. However, if I want
> to use some tool which need to lock file to save the file on the NFS
> server, e.g.
> vgcfgbackup -f $NFS_MNT_POINT/vg.cfg
> I get the message "lockd: cannot monitor 192.168.120.254", and the
> message shown on the /var/log/daemon.log:
> May 21 08:52:44 debian rpc.statd[1298]: STAT_FAIL to debian for SM_MON
> of 192.168.120.254
> May 21 08:52:44 debian rpc.statd[1298]: No canonical hostname found for
> 192.168.120.254
[...]
nfs-utils 1.2.2 includes the change:
commit 8ce130c4c828b9d13d429f22160f992b9c1d45cd
Author: Chuck Lever <chuck.lever@xxxxxxxxxx>
Date: Thu Jan 14 12:24:15 2010 -0500
statd: Support IPv6 in sm_mon_1_svc()
This appears to have removed support for IPv4 literals. Was this
intentional?
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part
