#95 NFS-server, nlockmgr and status daemos missing

v0.66
closed
5
2014-09-04
2006-06-18
ingo
No

I am unable to mount a NFS-export from most of my PC's.

Reason is, they cannot connect to nlockmgr for
file-locking, so NLM-Client does not start.

All other things are fine 'showexp FreeNAS' properly
reports exported resouces.

nlockmgr usually also is necessary to control access
rights on basis of UID/GID.
Such types of NFS-servers were formely used on System V
(SUN/solaris), but nowadays also FreeBSD and all Linux
systems use a full featured NFS-server providing
nlockmgr and status daemons.

For completeness here the output of 'rpcinfo -p':

FreeNAS (cannot mount from my clients)
Programm Vers Proto Anschlu├č
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100000 4 7 111 portmapper
100000 3 7 111 portmapper
100000 2 7 111 portmapper
100005 1 udp 765 mountd
100005 3 udp 765 mountd
100005 1 tcp 740 mountd
100005 3 tcp 740 mountd
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs

and here a 'normal' NFS-server where there are no problems:
100000 2 udp 111 portmapper
100000 2 tcp 111 portmapper
100005 1 tcp 62866 mountd
100005 3 tcp 62866 mountd
100005 1 udp 49168 mountd
100005 3 udp 49168 mountd
100024 1 udp 49171 status
100021 1 udp 49179 nlockmgr
100021 4 udp 49179 nlockmgr
100021 1 tcp 62867 nlockmgr
100021 2 tcp 62867 nlockmgr
100021 3 tcp 62867 nlockmgr
100021 4 tcp 62867 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs

Is there any chance to get the NFS-server updated (also
important for 0.7 version, where access on user/group
is planned). Also the portmap-server nowadays is
'portmap' and no longer 'rpcbind'.

I really would prefer to switch from 'eisfair' to
FreeNAS, but without working NFS I cannot use it.
I am quite sure, that I have set up allcorrect.

Best regards,
Ingo

Discussion

  • ingo

    ingo - 2006-06-29

    Logged In: YES
    user_id=1540519

    Maybe it helps to trace the root-cause for my mounting
    problems. Here I report the NFS-related part of the syslog
    from Linux based 'eisfair' server starting up where I do not
    have any problems with NFS:

    ....
    Starting NFSserver ...
    - sunrpc ...
    - lockd ...
    - nfsd ...
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    - portmap ...
    - rpc.statd ...
    - rpc.rquotad ...
    - rpc.nfsd ...
    - rpc.mountd ...
    .......

    I am just a user and no programmer, but my idea is that the
    missing 'lock-daemon' or at least the fact that it is not
    registered with 'portmap' is responsible for the failure of
    mounting.

    Is there any way to add that manually to FreeNAS?

    Best regards,
    Ingo

     
  • ingo

    ingo - 2006-06-29

    Logged In: YES
    user_id=1540519

    Maybe it helps to trace the root-cause for my mounting
    problems. Here I report the NFS-related part of the syslog
    from Linux based 'eisfair' server starting up where I do not
    have any problems with NFS:

    ....
    Starting NFSserver ...
    - sunrpc ...
    - lockd ...
    - nfsd ...
    Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
    - portmap ...
    - rpc.statd ...
    - rpc.rquotad ...
    - rpc.nfsd ...
    - rpc.mountd ...
    .......

    I am just a user and no programmer, but my idea is that the
    missing 'lock-daemon' or at least the fact that it is not
    registered with 'portmap' is responsible for the failure of
    mounting.

    Is there any way to add that manually to FreeNAS?

    Best regards,
    Ingo

     
  • Olivier Cochard-Labbe

    Logged In: YES
    user_id=1370551

    I've added this 2 dameons for the next release:
    rpc.statd and rpc.lockd

    Now a rpcinfo give me this information:

    [root@vm /usr/local/freenas]# rpcinfo -p 192.168.254.5
    program vers proto port service
    100000 4 tcp 111 rpcbind
    100000 3 tcp 111 rpcbind
    100000 2 tcp 111 rpcbind
    100000 4 udp 111 rpcbind
    100000 3 udp 111 rpcbind
    100000 2 udp 111 rpcbind
    100000 4 local 111 rpcbind
    100000 3 local 111 rpcbind
    100000 2 local 111 rpcbind
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100005 1 udp 716 mountd
    100005 3 udp 716 mountd
    100005 1 tcp 928 mountd
    100005 3 tcp 928 mountd
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100021 0 udp 794 nlockmgr
    100021 1 udp 794 nlockmgr
    100021 3 udp 794 nlockmgr
    100021 4 udp 794 nlockmgr
    100021 0 tcp 741 nlockmgr
    100021 1 tcp 741 nlockmgr
    100021 3 tcp 741 nlockmgr
    100021 4 tcp 741 nlockmgr
    100024 1 udp 854 status
    100024 1 tcp 738 status

    Is ok for you ?

     
  • ingo

    ingo - 2006-07-01

    Logged In: YES
    user_id=1540519

    Hi Oliver,

    that is really great, many many thanks!

    That really looks perfect, I do not mind whether high or
    reserved port numbers (< 1024) are used. Seems exeactly what
    my clients are missing;-)

    I'll also report test results here as soon as next version
    is available. I think FreeNAS is exactly what many users are
    missing: easy to use, configured by web-browser (operating
    system independant) and most important: designed for
    CF-compatibility (which also includes DOM=disk on module),
    and it is ideal for reusing 'old hardware'.

    My best regards,
    Ingo

     

Log in to post a comment.