From: Paul Libert <Paul.Libert@naturalsciences.be>
To: nfs@lists.sourceforge.net
Subject: kernel nlockmgr not registred with port mapper
Date: Fri, 13 Aug 2004 12:02:34 +0200 [thread overview]
Message-ID: <411C91BA.10506@naturalsciences.be> (raw)
[-- Attachment #1: Type: text/plain, Size: 2929 bytes --]
Dear List,
Solution to this problem should be easy but I'm to blind to find out so
...
I'm having problem with to acquire locks on file over a nfs mounted
filesystem.
Client system is a Debian Linux with 2.4.25 Debian packaged kernel
Server system is a Debian Linux with 2.4.24 Debian packaged kernel or
2.6.6 Debian packaged kernel.
After looking on the system, it appears that a 'rpcinfo -p' on both
server shows no nlockmgr :
Server 1 :
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 882 status
100024 1 tcp 885 status
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 897 mountd
100005 2 udp 897 mountd
100005 1 tcp 900 mountd
100005 2 tcp 900 mountd
Server 2 :
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 795 rquotad
100011 2 udp 795 rquotad
100011 1 tcp 798 rquotad
100011 2 tcp 798 rquotad
100024 1 udp 846 status
100024 1 tcp 849 status
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 953 mountd
100005 2 udp 953 mountd
100005 1 tcp 956 mountd
100005 2 tcp 956 mountd
390113 1 tcp 7937
Client has the nlockmgr as a registred service :
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100011 1 udp 953 rquotad
100011 2 udp 953 rquotad
100011 1 tcp 956 rquotad
100011 2 tcp 956 rquotad
100024 1 udp 793 status
100024 1 tcp 796 status
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 805 mountd
100005 2 udp 805 mountd
100005 1 tcp 808 mountd
100005 2 tcp 808 mountd
390113 1 tcp 7937
100021 1 udp 52638 nlockmgr
100021 3 udp 52638 nlockmgr
100021 4 udp 52638 nlockmgr
100021 1 tcp 56348 nlockmgr
100021 3 tcp 56348 nlockmgr
100021 4 tcp 56348 nlockmgr
So obviously, my problem is there.
I investigated further and found out that on both server, the 'lockd'
kernel module was not loaded.
I tought I had found my problem and issused a 'modprobe lockd'
So now, kernel module is loaded but the nlockmgr is still not registred
on portmap.
I've tried restartinf the portmapper and reloading the rpc.server but it
doesn't solve my problem.
Unloading and reloading the kernel module doesn't change anything.
It must be obvious but I keep missing it ...
Any help will be very much appreciated.
Best regards.
Paul Libert
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next reply other threads:[~2004-08-13 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-13 10:02 Paul Libert [this message]
[not found] ` <20040813104412.GY3516@hyperion.jason.nl>
2004-08-13 11:11 ` kernel nlockmgr not registred with port mapper Paul Libert
2004-08-13 12:22 ` Paul Libert
2004-08-13 16:14 ` Trond Myklebust
2004-08-13 16:32 ` Olaf Kirch
2004-08-18 9:40 ` Paul Libert
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=411C91BA.10506@naturalsciences.be \
--to=paul.libert@naturalsciences.be \
--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.