On Fri, Sep 07, 2007 at 05:49:55PM +0200, Wolfgang Walter wrote: > Hello, > > we upgraded the kernel of a nfs-server from 2.6.17.11 to 2.6.22.6. Since then > we get the message > > lockd: too many open TCP sockets, consider increasing the number of nfsd > threads > lockd: last TCP connect from ^\\236^\É^D > > 1) These random characters in the second line are caused by a bug in > svc_tcp_accept. > I already posted this patch on netdev@vger.kernel.org:
Thanks, I've applied that. (The bug is a little subtle: there's actually two previous __svc_print_addr() calls which might have initialized "buf" correctly, and it's not obvious that the second isn't always called (since it's in a dprintk, which is a macro that expands into a printk inside a conditional)). > with this patch applied one gets something like > > lockd: too many open TCP sockets, consider increasing the number of > nfsd threads lockd: last TCP connect from 10.11.0.12, port=784 > > > 2) The number of nfsd threads we are running on the machine is 1024. > So this is not the problem. It seems, though, that in the case of > lockd svc_tcp_accept does not check the number of nfsd threads but the > number of lockd threads which is one. As soon as the number of open > lockd sockets surpasses 80 this message gets logged. This usually > happens every evening when a lot of people shutdown their workstation. So to be clear: there's not an actual problem here other than that the logs are getting spammed? (Not that that isn't a problem in itself.) > 3) For unknown reason these sockets then remain open. In the morning > when people start their workstation again we therefor not only get a > lot of these messages again but often the nfs-server does not proberly > work any more. Restarting the nfs-daemon is a workaround. Hm, thanks. --b. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
