From owner-freebsd-current@FreeBSD.ORG Fri Oct 24 05:14:07 2003 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 6979316A4B3 for ; Fri, 24 Oct 2003 05:14:07 -0700 (PDT) Received: from mailhost.stack.nl (vaak.stack.nl [131.155.140.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AC8143FB1 for ; Fri, 24 Oct 2003 05:14:06 -0700 (PDT) (envelope-from marcolz@stack.nl) Received: by mailhost.stack.nl (Postfix, from userid 65534) id 748021F006; Fri, 24 Oct 2003 14:14:05 +0200 (CEST) Received: from turtle.stack.nl (turtle.stack.nl [2001:610:1108:5010:2e0:81ff:fe22:51d8]) by mailhost.stack.nl (Postfix) with ESMTP id 9C02D1F001; Fri, 24 Oct 2003 14:14:04 +0200 (CEST) Received: by turtle.stack.nl (Postfix, from userid 333) id 8B72A1CC71; Fri, 24 Oct 2003 14:14:04 +0200 (CEST) Date: Fri, 24 Oct 2003 14:14:04 +0200 From: Marc Olzheim To: Poul-Henning Kamp Message-ID: <20031024121404.GA3077@stack.nl> References: <20031024111903.GA2554@stack.nl> <7954.1066995018@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7954.1066995018@critter.freebsd.dk> X-Operating-System: FreeBSD turtle.stack.nl 5.1-CURRENT FreeBSD 5.1-CURRENT X-URL: http://www.stack.nl/~marcolz/ User-Agent: Mutt/1.5.4i X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on vaak.stack.nl X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 cc: Marc Olzheim cc: Soren Schmidt cc: current@freebsd.org Subject: Re: Anyone seeing any NFS lockups/weirdness with latest (ish) current?? 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, 24 Oct 2003 12:14:07 -0000 On Fri, Oct 24, 2003 at 01:30:18PM +0200, Poul-Henning Kamp wrote: > You may want to try this patch, Kirk sent it to me in response to a > case where my NFS-server hung during snapshot processing. > > I have only just managed to put it on my server so I don't know if > it solves the problem or not. Hmm, my NFS server stays ok; it's the client that has problems. Until somewhere this week, the following occurred: prompt> portupgrade -rR wv-0.7.5 ---> Upgrading 'imake-4.3.0' to 'imake-4.3.0_1' (devel/imake-4) ---> Building '/usr/ports/devel/imake-4' ===> Cleaning for perl-5.6.1_14 ===> Cleaning for imake-4.3.0_1 ===> Extracting for imake-4.3.0_1 >> Checksum OK for xc/X430src-1.tgz. >> Checksum OK for xc/X430src-3.tgz. [... ctrl-t (stty status) (15 seconds interval):] load: 2.43 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k load: 2.40 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k load: 2.34 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k load: 2.17 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k load: 2.05 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k load: 2.00 cmd: tar 12295 [nfsfsync] 0.09u 4.16s 2% 544k In other words, the 'tar' is dead in the water. Since somewhere this week, it not only hangs up that specific process, but all processes that try using NFS hang themselves up and eventually the machine reboots... I haven't produced a crash dump yet. The NFS server I use runs FreeBSD 4 and is mounted by a lot of FreeBSD 4 machines that do not have this problem. Zlo