kernel nlockmgr not registred with port mapper

kernel nlockmgr not registred with port mapper

[Paul Libert]

[-- 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 --]

Re: kernel nlockmgr not registred with port mapper

[Paul Libert]

[-- Attachment #1: Type: text/plain, Size: 744 bytes --]

Gerhard,

All of the three machines are running NFSServer and are 'exports'ing 
filesystems.

Paul

Gerhard den Hollander wrote:

> * Paul Libert <Paul.Libert@naturalsciences.be> (Fri, Aug 13, 2004 at 12:02:34PM +0200)
> 
>>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.
> 
> 
> make sure both machines are running an nfsserver, and make sure both
> machines are exporting a file system
> (yes, indeed, the *client* must be running an NFServer and MUST be
> exporting a filesystem as well.
> 
> Currently listening to: ph2004-08-09d103
> 
> 	Gerhard,  (faliquid@xs4all.nl)	== The Acoustic Motorbiker == 	


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

Re: kernel nlockmgr not registred with port mapper

[Paul Libert]

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

OK, forget about it.
Indeed to have nlockmgr appear as a registred portmap service, you need 
to have a nfs client connection active of the server (not only exporting 
a filesystem but mounting one ...).
A bit devious not ?

Thanks for the infor it helped me anyway.

Regards.

Paul

Gerhard den Hollander wrote:

> * Paul Libert <Paul.Libert@naturalsciences.be> (Fri, Aug 13, 2004 at 12:02:34PM +0200)
> 
>>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.
> 
> 
> make sure both machines are running an nfsserver, and make sure both
> machines are exporting a file system
> (yes, indeed, the *client* must be running an NFServer and MUST be
> exporting a filesystem as well.
> 
> Currently listening to: ph2004-08-09d103
> 
> 	Gerhard,  (faliquid@xs4all.nl)	== The Acoustic Motorbiker == 	


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]

Re: kernel nlockmgr not registred with port mapper

[Trond Myklebust]

P=E5 fr , 13/08/2004 klokka 06:02, skreiv Paul Libert:
> Dear List,
>=20
> Solution to this problem should be easy but I'm to blind to find out so=20
>    ...
>=20
> I'm having problem with to acquire locks on file over a nfs mounted=20
> filesystem.
>=20
> 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=20
> 2.6.6 Debian packaged kernel.
>=20
> After looking on the system, it appears that a 'rpcinfo -p' on both=20
> server shows no nlockmgr :
>=20
> 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
>=20
<snip>
> It must be obvious but I keep missing it ...

Looks to me as if you are using the user space NFS server. That never
had any support for the NLM locking protocol. In fact IIRC the addition
of locking support was one of the main motivations at the time for
writing the kernel NFS server (correct me if I'm wrong there Olaf).

Cheers,
  Trond


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: kernel nlockmgr not registred with port mapper

[Olaf Kirch]

On Fri, Aug 13, 2004 at 12:14:51PM -0400, Trond Myklebust wrote:
> Looks to me as if you are using the user space NFS server. That never
> had any support for the NLM locking protocol. In fact IIRC the addition
> of locking support was one of the main motivations at the time for
> writing the kernel NFS server (correct me if I'm wrong there Olaf).

That's right. Doing lockd in user space is horrible.

Olaf
-- 
Olaf Kirch     |  The Hardware Gods hate me.
okir@suse.de   |
---------------+ 


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

Re: kernel nlockmgr not registred with port mapper

[Paul Libert]

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

Olaf Kirch wrote:

> On Fri, Aug 13, 2004 at 12:14:51PM -0400, Trond Myklebust wrote:
> 
>>Looks to me as if you are using the user space NFS server. That never
>>had any support for the NLM locking protocol. In fact IIRC the addition
>>of locking support was one of the main motivations at the time for
>>writing the kernel NFS server (correct me if I'm wrong there Olaf).
> 
> 
> That's right. Doing lockd in user space is horrible.
> 
> Olaf

Got it !

Switching to kernel-space server solved my problem !

Thanks for the help.

Regards.

Paul

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]