From: Ben Hutchings <ben@decadent.org.uk>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Steven Shiau <steven@nchc.org.tw>,
579397@bugs.debian.org, linux-nfs@vger.kernel.org
Subject: Re: Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254
Date: Sat, 22 May 2010 02:38:48 +0100 [thread overview]
Message-ID: <1274492328.11828.3.camel@localhost> (raw)
In-Reply-To: <4BF71C27.7070309@nchc.org.tw>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
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@oracle.com>
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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2010-05-22 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BF71C27.7070309@nchc.org.tw>
2010-05-22 1:38 ` Ben Hutchings [this message]
2010-05-24 15:22 ` Bug#579397: STAT_FAIL to debian for SM_MON of 192.168.120.254, No canonical hostname found for 192.168.120.254 Chuck Lever
2010-06-03 21:08 ` Chuck Lever
2010-06-05 20:29 ` Ben Hutchings
2010-06-09 14:41 ` Steven Shiau
2010-07-06 17:05 ` Chuck Lever
2010-08-08 4:59 ` Ben Hutchings
2010-08-08 16:55 ` Chuck Lever
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=1274492328.11828.3.camel@localhost \
--to=ben@decadent.org.uk \
--cc=579397@bugs.debian.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steven@nchc.org.tw \
/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;
as well as URLs for NNTP newsgroup(s).