From owner-freebsd-hackers@FreeBSD.ORG Thu Jul 10 00:12:38 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA5D737B401 for ; Thu, 10 Jul 2003 00:12:38 -0700 (PDT) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B7243F3F for ; Thu, 10 Jul 2003 00:12:38 -0700 (PDT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 19aVbY-000Mxf-00 for freebsd-hackers@FreeBSD.org; Thu, 10 Jul 2003 10:12:36 +0300 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-hackers@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Jul 2003 10:12:36 +0300 From: Danny Braniss Message-Id: Subject: NetApp and 'nfs send error 32' X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jul 2003 07:12:39 -0000 hi all, googling shows this not to be anything new, but ... it happend when we enabled tcp/nfs on our NetApp fileservers. so the question is: 1- is it serious - it doesn't seem so ... 2- can it be ignored? the main problem is that to turn it off, i have to reboot some 600 machines :-( thanks, danny