From: Roger Leigh <roger.leigh@epictechnology.co.uk>
To: nfs@lists.sourceforge.net
Subject: rpc.statd: Received erroneous SM_UNMON request
Date: Thu, 28 Oct 2004 15:03:02 +0100 [thread overview]
Message-ID: <20041028140302.GA7584@epictechnology.co.uk> (raw)
Hi folks,
I'm getting a lot of these messages in my logs, and also hangs of up to
a minute on client machines during which a couple of these messages are
logged in the server (the client starts responding immediately after the
second message). I've checked past posts with this problem, which
seemed to suggest
- rpc.statd couldn't write /var/lib/nfs[/sm[.bak]]
(this is not a problem)
- the FQDN ("hostname -f") didn't match "uname -n"
(they are identical on the server and client after I put the FQDN in
/etc/hostname to correct uname -n)
The server has this export:
/srv/epic *(rw,sync,secure_locks,no_root_squash)
and the client has these mounts:
automount(pid2036) on /var/autofs/net type autofs
(rw,fd=5,pgrp=2036,minproto=2,maxproto=4)
till2:/home/epic on /var/autofs/net/till2/home/epic type nfs
(rw,nosuid,nodev,hard,intr,nfsvers=3,udp,rsize=8192,wsize=8192,addr=10.0.0.156)
This is using autofs4 with Linux 2.6.8.1 on both machines.
I've tried a number of NFS options, including tcp/udp, rsize/wsize,
checked tcp wrappers are permissive enough, but I've not been able to
identify the cause of the problem. The hanging /may/ have been due
to too restrictive tcp wrappers (hosts.allow) on one of the machines,
but after relaxing the restrictions the SM_UNMON errors are still
being logged.
The application running on the client is a DOS database application
(Clipper-like) using database files on the server running under DOSEMU.
It uses record locking to lock regions of the file. This part appears
to work well (it cooperates with locks taken by Samba from Windows
clients running the same program),but the hangs are not so good.
Are there any other known causes of this problem?
Is there anything else I can check?
This is what gets logged on the server:
Oct 27 11:35:25 till2 kernel: lockd: request from 0a00009d
Oct 27 11:35:25 till2 kernel: lockd: nlm_lookup_host(0a00009d, p=17,
v=4)
Oct 27 11:35:25 till2 kernel: lockd: host garbage collection
Oct 27 11:35:25 till2 kernel: lockd: nlmsvc_mark_resources
Oct 27 11:35:25 till2 kernel: lockd: delete host 10.0.0.157
Oct 27 11:35:25 till2 kernel: lockd: nsm_unmonitor(10.0.0.157)
Oct 27 11:35:25 till2 rpc.statd[2757]: Received erroneous SM_UNMON
request from till2.lan for 10.0.0.157
Oct 27 11:35:25 till2 kernel: lockd: creating host entry
Oct 27 11:35:25 till2 kernel: lockd: nsm_monitor(10.0.0.157)
Oct 27 11:35:25 till2 kernel: nsm: xdr_decode_stat_res status 0 state 83
Oct 27 11:35:25 till2 kernel: lockd: nlm_file_lookup(02000001 0400fe00
00010001 00010804 13bb0bdb 00010796)
Oct 27 11:35:25 till2 kernel: lockd: creating file for (02000001
0400fe00 00010001 00010804
13bb0bdb 00010796)
Oct 27 11:35:25 till2 kernel: lockd: found file dde34800 (count 0)
Oct 27 11:35:25 till2 kernel: lockd: nlmsvc_lock(dm-4/67588, ty=1,
pi=2229, 805306370-805306371, bl=0)
and this is the client log:
Oct 27 11:29:25 till1 kernel: lockd: release host 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: nlm_lookup_host(0a00009c, p=17,
v=4)
Oct 27 11:34:15 till1 kernel: lockd: host garbage collection
Oct 27 11:34:15 till1 kernel: lockd: nlmsvc_mark_resources
Oct 27 11:34:15 till1 kernel: lockd: delete host 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: nsm_unmonitor(10.0.0.156)
Oct 27 11:34:15 till1 rpc.statd[2099]: Received erroneous SM_UNMON
request from till1.lan for 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: creating host entry
Oct 27 11:34:15 till1 kernel: lockd: nlm_bind_host(0a00009c)
Oct 27 11:34:15 till1 kernel: lockd: nsm_monitor(10.0.0.156)
Oct 27 11:34:15 till1 kernel: nsm: xdr_decode_stat_res status 0 state 79
Oct 27 11:34:15 till1 kernel: lockd: nlm_bind_host(0a00009c)
Oct 27 11:34:15 till1 kernel: lockd: release host 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: get host 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: nlm_lookup_host(0a00009c, p=17,
v=4)
Oct 27 11:34:15 till1 kernel: lockd: get host 10.0.0.156
Oct 27 11:34:15 till1 kernel: lockd: nlm_bind_host(0a00009c)
Many thanks,
Roger
--
Roger Leigh
Printing on GNU/Linux? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848. Please sign and encrypt your mail.
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
reply other threads:[~2004-10-28 14:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041028140302.GA7584@epictechnology.co.uk \
--to=roger.leigh@epictechnology.co.uk \
--cc=nfs@lists.sourceforge.net \
/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.