From: Kasparek Tomas Subject: Re: [PATCH 0/3] NFS regression in 2.6.26?, "task blocked for more than 120 seconds" Date: Tue, 20 Jan 2009 16:03:01 +0100 Message-ID: <20090120150301.GG47559@fit.vutbr.cz> References: <20090109145638.GC47559@fit.vutbr.cz> <1231523966.7179.67.camel@heimdal.trondhjem.org> <20090110102458.GG47559@fit.vutbr.cz> <1231603200.29646.5.camel@heimdal.trondhjem.org> <20090112090404.GL47559@fit.vutbr.cz> <1231782009.7322.12.camel@heimdal.trondhjem.org> <1231809446.7322.17.camel@heimdal.trondhjem.org> <20090113152201.GD47559@fit.vutbr.cz> <20090116104802.GF47559@fit.vutbr.cz> <20090118130835.GH47559@fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-nfs@vger.kernel.org To: Trond Myklebust Return-path: Received: from kazi.fit.vutbr.cz ([147.229.8.12]:50078 "EHLO kazi.fit.vutbr.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757863AbZATPDG (ORCPT ); Tue, 20 Jan 2009 10:03:06 -0500 In-Reply-To: <20090118130835.GH47559@fit.vutbr.cz> Sender: linux-nfs-owner@vger.kernel.org List-ID: 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? The clients are different machines - Intel x AMD with different boards, NICs etc. The server is dead too, but it may recover after some time - I can not afford leaving it for longer time to see what happens. Thanks so far. -- Tomas Kasparek, PhD student E-mail: kasparek@fit.vutbr.cz CVT FIT VUT Brno, L127 Web: http://www.fit.vutbr.cz/~kasparek Bozetechova 1, 612 66 Fax: +420 54114-1270 Brno, Czech Republic Phone: +420 54114-1220 jabber: tomas.kasparek-2ASvDZBniIelVyrhU4qvOw@public.gmane.org GPG: 2F1E 1AAF FD3B CFA3 1537 63BD DCBE 18FF A035 53BC