http://bugzilla.novell.com/show_bug.cgi?id=519028 Summary: max_resvports > 1023 produce message kernel: lockd_up: makesock failed, error=-13, then mounts fail Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: dscott.lucas@gmail.com QAContact: qa@suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.11) Gecko/2009060200 SUSE/3.0.11-0.1 Firefox/3.0.11 Kernel version is 2.6.27 or 2.6.30. Opensuse 11.x. When max_resvport is set to 2048, 5000, etc., we get the following messages in /var/log/messages - kernel: lockd_up: makesock failed, error=-13. Either right away or shortly after setting max_resvport to a higher number/rebooting with the parameter set in sysctl.conf, nfs mounts completely fail. If we leave it set to only 1023, we run up against the nfs mount limit, which puts us between a rock and a hard place. In kernel version 2.6.18, opensuse 10.2, max_resvport=5000, this error never appears, and we have no problems with reserved port limits. here is the output of /proc/mounts on opensuse 11.1/2.6.27+ (doesn't work): icenas:/mnt/home/lucads2 /home/lucads2 nfs rw,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,nointr,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=204.134.163.111,mountvers=3,mountproto=udp,addr=204.134.163.111 0 0 /proc/mounts output on opensuse 10.2/2.6.18 (works): icenas:/mnt/home/lucads2 /home/lucads2 nfs rw,vers=3,rsize=1048576,wsize=1048576,hard,proto=tcp,timeo=600,retrans=3,sec=sys,addr=icenas 0 0 Reproducible: Always Steps to Reproduce: 1.bump max_resvport to 1500 or higher (typically 2048 or 5000) 2. 3. Actual Results: kernel: lockd_up: makesock failed, error=-13. appears in /var/log/messages Attempts to mount nfs shares fail Expected Results: No error, nfs mounts above 1023 work -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.