>> In 2 places the server stops responding. In both cases, the client seems >> to be sending a single TCP frame containing several COMPOUNDS containing >> READ requests (which should be legal) just prior to the hang. When the >> server doesn't respond, the client pings it with a RENEW, before it ends >> up severing the TCP connection and then retransmitting. > > And sometimes -- speaking only from the behavour I've seen, not from the > actual frames sent -- server does not respond to the RENEW too, in which > case the client reports "nfs server no responding", and on the next > renew it may actually respond. This happens too, but much more rare. > > During these stalls, ie, when there's no network activity at all, > the server NFSD threads are busy eating all available CPU. > > What does it all tell us? :) Hi, are there news on this issue? We see bad NFS performance on systems using Ubuntu 12.04 compared to systems using Ubuntu 10.04 that look similar. There are also two bug reports for Ubuntu with some information: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1006446 https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/879334 Chrsitoph -- 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
