On Sun, 2008-08-24 at 23:09 +0100, Ian Campbell wrote: > (added some quoting from previous mail to save replying twice) > > On Sun, 2008-08-24 at 15:19 -0400, Trond Myklebust wrote: > > On Sun, 2008-08-24 at 15:17 -0400, Trond Myklebust wrote: > > > >From the tcpdump, it looks as if the NFS server is failing to close the > > > socket, when the client closes its side. You therefore end up getting > > > stuck in the FIN_WAIT2 state (as netstat clearly shows above). > > > > > > Is the server keeping the client in this state for a very long > > > period? > > Well, it had been around an hour and a half on this occasion. Next time > it happens I can wait longer but I'm pretty sure I've come back from > time away and it's been wedged for at least a day. How long would you > expect it to remain in this state for?
The server should ideally start to close the socket as soon as it receives the FIN from the client. I'll have a look at the code. Trond ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
