Hi Jon, On Thursday 04 February 2010 19:09:37 Jon Forrest wrote: > > First of all, the Sun 7310 is one of those servers > that you "can't" login to. You manage it only > via a Web interface. > OK, sorry, not had such a beast under my fingers yet ;)
> I've set the server to use 500 NFS server threads. > Is it necessary to go above that? > That should be fine. > Both the Sun server, the switch, and all the compute nodes > in the cluster claim to support jumbo frames. That's why I'm asking. We've had some network components (e.g. HP) which did support 9k Jumbo frames, however going beyond 3-4.5k caused such a severe performance drop that it was not advisable. What I would do to make certain this is not a problem: (1) ping -s 8972 -Mdo <remote host> (try different payload sizes and remember that there might be some overhead in the switches needed) (2) Use netperf between different nodes and see if the performance is not drastically reduced with large jumbo frames. > Turning them off is something that I could > do, but I'd have to do it globally because this is > a per interface settings. There's no > way I can think of that would allow me to > keep jumbo frames on on only certain nodes > so that I could run a controlled experiment. > If above's stuff is working, there should be no need. > > I've looked this up and it might have something > to do with the problem. The trouble is that I can't > see when these error messages are generated so > I can't try to correlate them with the autofs > problem. Would it be possible for you to recompile the kernel with the same settings and enable timings in printk lines (under kernel hacking)? That might help, but might be some work to get working. Cheers Carsten _______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
