From: Wendy Cheng <wcheng@redhat.com>
To: Wendy Cheng <wcheng@redhat.com>
Cc: Neil Brown <neilb@suse.de>,
nfs@lists.sourceforge.net,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: lockd and statd
Date: Wed, 04 Apr 2007 19:00:47 -0400 [thread overview]
Message-ID: <46142E1F.8050000@redhat.com> (raw)
In-Reply-To: <46142B4F.1030507@redhat.com>
In case there are other changes that I'm not aware of. The kernel patch
is based on 2.6.21-rc4 kernel ... Wendy
> Trond Myklebust wrote:
>> On Wed, 2007-04-04 at 14:49 -0400, Wendy Cheng wrote:
>>
>>> I'm wondering what would be the reason(s) that the community
>>> version of Linux statd is put in user space ? Any one cares to give
>>> either a technical or historical explanation ?
>>>
>>
>> Off the cuff, I can think of 2 main reasons why it needs to be in user
>> space:
>> 1) It creates and maintains a directory hierarchy on permanent storage
>> (as opposed to in a pseudo filesystem).
>> 2) It needs to resolve addresses via DNS etc.
>>
>
> Ha! #2 happens to be my question.. Is there any reason why it has to
> be dnsname ? The following is my issue:
>
> While testing out the NLM failover patches, on Neil's new
> nfs-utils-1.1.0-rc1, sm_mon_1_svc() writes to /var/lib/nfs/sm using
> dnsname (say, for example, dhcp146.something.com), even the kernel has
> passed it a dotted IP address (say 192.168.24.146, since I can't use
> "nsm_use_hostnames" as lockd module param). Unfortunately, the
> sm_unmon_1_svc() doesn't do similar conversion. So when kernel side
> tries to delete the monitored name, I got:
>
> Apr 4 18:12:25 dhcp143 kernel: lockd: delete host
> dhcp146.perf.redhat.com
> Apr 4 18:12:25 dhcp143 kernel: lockd:
> nsm_unmonitor(dhcp146.perf.redhat.com)
> Apr 4 18:12:25 dhcp143 rpc.statd[4210]: unlink
> (/var/lib/nfs/sm/192.168.24.146): No such file or directory
>
> BTW, don't be fooled by above lockd trace (it printed out hostname but
> I'm very sure I passed in IPV4 dotted address as seen by the attached
> kernel statd patch).
>
> Oversight ? My configuration problem ? nfs-util bug ? my bug ? or I
> mis-understand the logic ?
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-04-04 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 7:11 lockd and statd Greg Bradner
2007-04-04 12:40 ` Trond Myklebust
2007-04-04 16:09 ` Greg Bradner
2007-04-04 17:33 ` Olaf Kirch
2007-04-04 18:49 ` Wendy Cheng
2007-04-04 21:34 ` Trond Myklebust
2007-04-04 22:48 ` Wendy Cheng
2007-04-04 23:00 ` Wendy Cheng [this message]
2007-04-04 23:22 ` Trond Myklebust
2007-04-10 8:47 ` Olaf Kirch
2007-04-10 19:36 ` Trond Myklebust
2007-04-10 20:16 ` Talpey, Thomas
2007-04-04 23:25 ` Neil Brown
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=46142E1F.8050000@redhat.com \
--to=wcheng@redhat.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.