From owner-freebsd-stable Fri Apr 5 21:15:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 32F8C37B41C for ; Fri, 5 Apr 2002 21:15:47 -0800 (PST) Received: from frejya.corp.netapp.com (frejya [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id g365Fjh18765; Fri, 5 Apr 2002 21:15:45 -0800 (PST) Received: from orbit-fe.eng (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.12.2/8.12.2/NTAP-1.4) with ESMTP id g365FjRt000041; Fri, 5 Apr 2002 21:15:45 -0800 (PST) Received: from localhost (kmacy@localhost) by orbit-fe.eng (8.11.6+Sun/8.11.6) with ESMTP id g365FiL22639; Fri, 5 Apr 2002 21:15:44 -0800 (PST) Date: Fri, 5 Apr 2002 21:15:44 -0800 (PST) From: Kip Macy To: aditya@grot.org Cc: freebsd-stable@freebsd.org Subject: NFS hang with fxp and Network Appliance fileserver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > If this is the "correct" method to deal with the fxp cards, then should > the text be amended or should the fxp driver be "fixed"? This sounds like it could be a flow control problem caused by NFS v2's abuse of fragmentation/reassembly when using large UDP packets. What are your mount options? Have you tried v3 with tcp? Many of our machines in the labs have 8255x based cards and none of them see this problem. That is not to say that your problem is not real, just that there is some key difference in configuration that we need to isolate. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message