From: Scott McDermott <vaxerdec@frontiernet.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Stange NFS messages - 2.2.18pre19
Date: Wed, 8 Nov 2000 21:15:38 -0500 [thread overview]
Message-ID: <20001108211538.C14262@vaxerdec> (raw)
In-Reply-To: <Pine.LNX.4.10.10011072326340.21756-100000@iq.rulez.org>
In-Reply-To: <Pine.LNX.4.10.10011072326340.21756-100000@iq.rulez.org>; from sape@iq.rulez.org on Tue, Nov 07, 2000 at 11:28:14PM +0100
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.
-
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 prev parent reply other threads:[~2000-11-09 2:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-07 22:28 Stange NFS messages - 2.2.18pre19 Sasi Peter
2000-11-09 2:15 ` Scott McDermott [this message]
2000-11-09 7:33 ` Sasi Peter
2000-11-09 11:57 ` Klaus Naumann
[not found] <20001109024949$4fc3@tornado.cs.columbia.edu>
2000-11-09 6:56 ` Ion Badulescu
2000-11-09 13:19 ` Alan Cox
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=20001108211538.C14262@vaxerdec \
--to=vaxerdec@frontiernet.net \
--cc=linux-kernel@vger.kernel.org \
/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