On Thu, 4 Sep 1997, Michael Douglass wrote:
Looking through the logs on the clients, we have "NFS server not responding" errors (for 0 sec duration) across all the clients. Those that beat more heavily on the NetApp (like one box that constitutes 70% of the traffic) has these every few minutes.
These occur using full duplex 100T and suns as clients as well. So I don't think that FDDI is the key. I think I remember reading that netapp had fixed this, or were working on a fix.
Yes, in more ancient times the network was the bottleneck (in general). Today, server loading is more likely the culprit, in general.
That's what I've found with our NetApps (2xF330s), which are both 100BaseT-connected to a Cisco Catalyst 5000. Previously they were also FDDI-connected (backups ran through the FDDI). Whenever we see "NFS server not responding" we immediately check 'systat' on the F330s and find that they're operating near peak, and the suspicion is (not being a NetApp designer) that response time is degraded enough that the NFS timers have timed out on the client waiting for a response.
We've gotten around this somewhat (not sure how useful it is though) by adjusting (raising) timeo in /etc/vfstab (Solaris 2.x). This lessens the number of error messages but I think that's just masking the true problem of response time.
-- Dave Pascoe | mailto:dave@mathworks.com | Voice: 508.647.7362 KM3T | http://www.mathworks.com | FAX: 508.647.7002 PGP fingerprint: 53 AD 71 88 2F AA 45 AC D0 2E 68 91 71 77 39 AF