[lkml]   [2000]   [Nov]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Stange NFS messages - 2.2.18pre19
On Wed, 8 Nov 2000 21:15:38 -0500, Scott McDermott <> 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
> 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.


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
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:45    [W:0.045 / U:3.452 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site