• Bug#607177: mountnfs: nolock test for portmap seems not to be enough

    From Mark Hindley@21:1/5 to Emmanuel Lacour on Mon Mar 10 11:00:01 2025
    Emmanuel,

    Sorry, please ignore my last response, I confused this with a different issue.

    On Wed, Dec 15, 2010 at 12:12:24PM +0100, Emmanuel Lacour wrote:
    Package: initscripts
    Version: 2.88dsf-13
    Severity: normal


    /etc/fstap:

    server:/home/foo /foo nfs rw,nolock 0 0

    /etc/network/nfsmount try to mount it at boot time and do it
    successfully, but in 1mn10s!

    Tracking this down I found that the nolock option implies that mountnfs doesn't start portmap.

    If I start portmap the mount take less than one second.

    here is the result in /proc/mounts without portmap:

    server:/home/foo /foo nfs rw,relatime,vers=3,rsize=262144,wsize=262144,namlen=255,hard,nolock,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.0.0.2,mountvers=3,mountport=58924,mountproto=udp,addr=1.2.3.4 0 0

    maybe one of those default options require portmap?

    Yes, very possibly.

    Reading nfs(5) I think it might be mountport and/or mountproto.

    On your system, where are those options configured? /etc/nfs.conf? /etc/exports on the server?

    Are you able to test or confirm?

    Mark

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)