From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 08:33:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F90216A4D3 for ; Fri, 2 Apr 2004 08:33:55 -0800 (PST) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECB6043D31 for ; Fri, 2 Apr 2004 08:33:54 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i32GXsgO042451; Fri, 2 Apr 2004 10:33:54 -0600 (CST) (envelope-from dan) Date: Fri, 2 Apr 2004 10:33:54 -0600 From: Dan Nelson To: Sean McNeil Message-ID: <20040402163353.GC6724@dan.emsphone.com> References: <1080882894.5980.26.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1080882894.5980.26.camel@server.mcneil.com> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: nfs server issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2004 16:33:55 -0000 In the last episode (Apr 01), Sean McNeil said: > I have googled and seen a great deal of talk about FreeBSD nfs client > issues, but haven't seen anything about server problems. I've now > tried with a Solaris 2.7, HPUX 11.11, and 2 different Linux boxes and > I get the same thing happening... > > If I mount an nfs partition on any of the above mentioned machines, > everything works fine until I try to copy a bunch of files over. For > instance, if I mount it at /mnt and do > > cd /localdisk; (cd /mnt; tar cf - .) | tar xvf - > > It will lock up hard. Linux is saying > > nfs: task xxxx can't get a request slot "tcpdump -s0" output might help here, I think. Do it from both machines and make sure no packets are being dropped, and then check to see what NFS request the client is trying to make that isn't getting processed. -- Dan Nelson dnelson@allantgroup.com