On 11/20/98 20:38:35 you wrote:
this happens. After eliminating that, my best advice would be to change the client mounts to use different NFS protocols... UDP instead of TCP, and/or v2 instead of v3. Doing so may prevent or may make it less likely that you'll 'tickle' the Netapp bug. Also, check out the different
Well, we have mostly v2 clients, but the v3 tcp client and the v3 udp clients have all seen exactly the same behaviour.
No, you misunderstand. The v3 clients or the tcp clients could be *causing* the bug to occur in the netapp, which then consumes resources to kill all clients. So, changing the clients to a different mechanism may avoid the problem. Get it?
Bruce
On Fri, 20 Nov 1998 sirbruce@ix.netcom.com wrote:
Well, we have mostly v2 clients, but the v3 tcp client and the v3 udp clients have all seen exactly the same behaviour.
No, you misunderstand. The v3 clients or the tcp clients could be *causing* the bug to occur in the netapp, which then consumes resources to kill all clients. So, changing the clients to a different mechanism may avoid the problem. Get it?
Now I do. Good point. I'll drop the v3 clients, and go back to only v2.
-
Matt Stein -
sirbruce＠ix.netcom.com