On Tue, 2009-01-20 at 16:03 +0100, Kasparek Tomas wrote: > On Sun, Jan 18, 2009 at 02:08:35PM +0100, Kasparek Tomas wrote: > > > > > The attached 2 patches have been tested using a server that was rigged > > > > > not to ever close the socket. They appear to work fine on my setup, > > > > > without the hang that you reported earlier. > > ... > > It seems that machines with this new kernel (tried on 10 other machines > > and the original client) may after few days get into state where they > > generate huge amounts (10000-100000pkt/s) of packets on another server they > > use (Linux 2.6.26.62, but the same behaviour with other kernels I tried - > > 2.6.24.7, 2.6.22.19, 2.6.27.10). It seems packets are quiet small as the > > flow on server is about 5-10MB/s. (probably) Each packet generates an answer. > > With this flow it is hard to get more info and the server is production > > one, so for now I only know it goes from these clients and end on tcp port > > 2049 on that server. It kills just this server, communication with the > > previously problematic (FreeBSD machines) is fine now. > > Hi all, > > configrming that the problem is with machines with 2.6.27.10+trond's > patches. Do not have more info about what's there on network, the only new > thing I can add is that the client is dead not reacting even on keyborad or > anything else. Trond, would you have and idea what to try now or what other > information to find to get any further in this? A binary wireshark dump of the traffic between one such client and the server would help. Cheers Trond -- Trond Myklebust Linux NFS client maintainer NetApp Trond.Myklebust@xxxxxxxxxx www.netapp.com -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
