On Tue, 2008-12-02 at 16:22 +0100, Kasparek Tomas wrote: > On Sun, Nov 30, 2008 at 07:29:40PM -0500, Trond Myklebust wrote: > > On Sun, 2008-11-30 at 19:17 -0500, Trond Myklebust wrote: > > > Can you see if the following 3 patches help? They're against 2.6.28-rc6, > > > but afaics the problems are pretty much the same on 2.6.26. > > > > Sorry... I forgot to add that these 3 patches need to be applied to the > > nfs server, not the client. > > Hi, > > I have the problem on client side and can not change server (FreeBSD 7.0). > these patches does not change the situation (and they are probably not > supposed to do so, just giving it a try). After few minutes I got this on > the client with 2.6.28-rc6 with patches: > > tcp 0 0 147.229.12.146:674 147.229.176.14:2049 FIN_WAIT2 > > Applying reverse e06799f958bf7f9f8fae15f0c6f519953fb0257c suggested by Ian > does help on the other side (with 2.6.27.4). Then I suggest working around the problem by reducing the value of the sysctl net.ipv4.tcp_fin_timeout on the client. -- 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
