From: Ion Badulescu <ionut@moisil.cs.columbia.edu>
To: Scott McDermott <vaxerdec@frontiernet.net>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Stange NFS messages - 2.2.18pre19
Date: Wed, 8 Nov 2000 22:56:03 -0800 [thread overview]
Message-ID: <200011090656.eA96u3Y22945@moisil.dev.hydraweb.com> (raw)
In-Reply-To: <20001109024949$4fc3@tornado.cs.columbia.edu>
On Wed, 8 Nov 2000 21:15:38 -0500, Scott McDermott <vaxerdec@frontiernet.net> wrote:
> Sasi Peter on Tue 7/11 23:28 +0100:
>> I'm getting this under moderate NFS load:
>> Nov 6 17:39:56 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>> Nov 6 17:40:08 iq kernel: svc: unknown program 100227 (me 100003)
>> Nov 6 19:06:11 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>> Nov 6 19:38:48 iq kernel: svc: server socket destroy delayed (sk_inuse: 1)
>>
>> What do these means? Is this a kernel bug?
>
> Your Suns are using TCP mounts, this got introduced into 2.2.18
> somewhere and is a bit broken, do a patch -R with
> ftp://oss.sgi.com/www.projects/nfs3/download/nfs_tcp-2.2.17.dif and
> these go away. Suns try TCP mounts first. Be careful to unmount them
> first or they will hang waiting for the TCP server to come back up.
I really really think this should be backed out -- or at the very least
disabled. The code wasn't part of the dhiggen merge, it wasn't tested,
and it doesn't work well. Heck, it's still experimental and not recommended
in 2.4.0-test.
What's worse, it will burn everybody out there who is using am-utils or
an automounter that tries TCP mounts first. NFS/UDP server support in 2.2.18
is so much better than in previous versions, it would a shame to ruin
it with this ill-fated patch.
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-11-09 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001109024949$4fc3@tornado.cs.columbia.edu>
2000-11-09 6:56 ` Ion Badulescu [this message]
2000-11-09 13:19 ` Stange NFS messages - 2.2.18pre19 Alan Cox
2000-11-07 22:28 Sasi Peter
2000-11-09 2:15 ` Scott McDermott
2000-11-09 7:33 ` Sasi Peter
2000-11-09 11:57 ` Klaus Naumann
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=200011090656.eA96u3Y22945@moisil.dev.hydraweb.com \
--to=ionut@moisil.cs.columbia.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=vaxerdec@frontiernet.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox