2.6.24.Hi, J. Bruce Fields wrote: >> In the standard set-up many connections get into the box (tcp connection >> status SYN_RECV) but those fall over after some time and stay in >> CLOSE_WAIT state until I restart the nfs-kernel-server. Typically that >> looks like (netstat -an): > > That's interesting! But I'm not sure how to figure this out. > > Is it possible to get a network trace that shows what's going on? > In principle yes, but (1) it's huge. I only get this when doing this with 500-1000 clients starting at about the same time (2) It seems that I don't get a full trace, i.e. the session seem to be incomplete - sometimes I only see a single packet with FIN set. I tried doing this both with wireshark running locally and with ntap's capturing device. > What happens on the clients? > In the logs (/var/log/daemon.log) I only see that the mount request fails in different ways. Apr 9 12:07:55 n0078 automount[26838]: >> mount: RPC: Timed out Apr 9 12:07:55 n0078 automount[26838]: mount(nfs): nfs: mount failure d14:/data on /atlas/data/d14 Apr 9 12:07:55 n0078 automount[26838]: failed to mount /atlas/data/d14 Apr 9 12:18:56 n0078 automount[27977]: >> mount: RPC: Remote system error - Connection timed out Apr 9 12:18:56 n0078 automount[27977]: mount(nfs): nfs: mount failure d14:/data on /atlas/data/d14 I have not yet run tshark in the background on many nodes to see if I can capture the client's view. Would that be beneficial? > What kernel version are you using?--b. 2.6.24.4 on Debian Etch Right now, it seems that running 196 nfsd plus 64 threads for mountd solves the problem for the time being. Although it would be nice to understand these "magic" numbers ;) Thanks! Carsten ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ NFS maillist - NFS@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/nfs _______________________________________________ Please note that nfs@xxxxxxxxxxxxxxxxxxxxx is being discontinued. Please subscribe to linux-nfs@xxxxxxxxxxxxxxx instead. http://vger.kernel.org/vger-lists.html#linux-nfs -- 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
