From: Jan Kasprzak <kas@fi.muni.cz>
To: nfs@lists.sourceforge.net
Cc: unix@fi.muni.cz
Subject: Re: mountd gives "illegal port"
Date: Wed, 27 Oct 2004 18:12:57 +0200 [thread overview]
Message-ID: <20041027161256.GC4333@fi.muni.cz> (raw)
In-Reply-To: <20041027124228.GJ4724@fi.muni.cz>
Jan Kasprzak wrote:
: I have discovered the following problem in Linux NFS: When you mount
: many filesystems from the same server, mountd sometimes refuses the
: request with "illegal port" message in syslog.
Well, the mountd is probably OK, and it is the client who runs
out of privileged ports. netstat -ta on the client looks like this:
tcp 0 0 nfs-client.fi.muni.cz:880 nfs-server.fi.muni.c:sunrpc TIME_WAIT
tcp 0 0 nfs-client.fi.muni.cz:883 nfs-server.fi.muni.c:sunrpc TIME_WAIT
tcp 0 0 nfs-client.fi.muni.cz:884 nfs-server.fi.muni.c:sunrpc TIME_WAIT
tcp 0 0 nfs-client.fi.muni.cz:887 nfs-server.fi.muni.c:sunrpc TIME_WAIT
tcp 0 0 nfs-client.fi.muni.cz:888 nfs-server.fi.muni.c:sunrpc TIME_WAIT
tcp 0 0 nfs-client.fi.muni.cz:891 nfs-server.fi.muni.c:sunrpc TIME_WAIT
[...]
The solution might be to query portmap over UDP from the NFS client
instead of TCP. Or to query portmap from an unprivileged port (why we
send query to portmap from privileged port anyway?).
I have even tried echo 2 > /proc/sys/net/ipv4/tcp_fin_timeout,
but this did not solve the problem - connections to server's portmap
remain for 60 seconds in FIN_WAIT.
-Yenya
--
| Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> |
| GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E |
| http://www.fi.muni.cz/~kas/ Czech Linux Homepage: http://www.linux.cz/ |
> Whatever the Java applications and desktop dances may lead to, Unix will <
> still be pushing the packets around for a quite a while. --Rob Pike <
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-10-27 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 12:42 mountd gives "illegal port" Jan Kasprzak
2004-10-27 15:45 ` J. Bruce Fields
2004-10-27 16:23 ` Jan Kasprzak
2004-10-27 16:39 ` J. Bruce Fields
2004-10-27 16:40 ` Jan Kasprzak
2004-10-27 18:28 ` Peter Astrand
2004-10-27 16:12 ` Jan Kasprzak [this message]
2004-10-27 21:04 ` Michael Richardson
2004-10-27 21:13 ` Jan Kasprzak
2004-10-27 22:19 ` Michael Richardson
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=20041027161256.GC4333@fi.muni.cz \
--to=kas@fi.muni.cz \
--cc=nfs@lists.sourceforge.net \
--cc=unix@fi.muni.cz \
/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.