Hi,
On Tue, 13 Mar 2007, Neil Horman wrote:
I'll summarize what our problems and config's are.
Problems - lockups on ethernet controllers under heavy NFS loads
(sometimes driver can/will reset, sometimes not)
systems completely lock up
Hardware - Supermicro H8SSL-i with onboard Broadcom 5704's (both clients
and servers)
Server config - 2.6.19 kernel (thus tg3 ver 3.69)
nfs-utils-1.0.7-13 FC4
NIC running at 4500 MTU
What on earth is that? I assume you are configured for jumbo frames
through your whole network, but why not bump your mtu all the way up to
9000 then?
yes, we're configured to allow upto 9000 MTU, but we're using 4500 as that
was the intersection of performance with regards to switch topology (don't
ask), cpu overhead with the tg3 driver (in 2.6.11, at least), and
throughput (using a variety of canned benchmarky things).
Does the problem persist if you only use a 1500 byte MTU?
Don't know, we're theoretically in production mode (when the machines are
all up that the same time).
Failure caused by users building software in automounted FS's.
Can you get a sysrq-t when the system locks up?
Will try the next time it craps out, and I can still get console access.
Thanks,
Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
