From owner-freebsd-current@FreeBSD.ORG Fri Jan 14 01:15:06 2005 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 0F9A616A4CE for ; Fri, 14 Jan 2005 01:15:06 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B74C643D31 for ; Fri, 14 Jan 2005 01:15:04 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id j0E1DtTe010031 for ; Fri, 14 Jan 2005 11:43:55 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 14 Jan 2005 11:44:55 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id j0E15xQ31995 for ; Fri, 14 Jan 2005 11:35:59 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK38C6CM; Fri, 14 Jan 2005 11:35:40 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id j0E16c2D050362 for ; Fri, 14 Jan 2005 11:36:38 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id j0E16ckA050361 for freebsd-current@freebsd.org; Fri, 14 Jan 2005 11:36:38 +1030 (CST) (envelope-from wilkinsa) Date: Fri, 14 Jan 2005 11:36:38 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20050114010638.GT49309@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: NFS problems, locking up 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, 14 Jan 2005 01:15:06 -0000 0n Wed, Jan 12, 2005 at 08:53:11PM +0000, Robert Watson wrote: > >On Wed, 12 Jan 2005, Daniel Eriksson wrote: > >> I'm still having problems with NFS locking up when moving large amounts >> of data over it on 6-CURRENT from 2005.01.11.05.00.00. This problem has >> persisted for a long time now, and the only thing that seems to cure it >> is running the network stack with giant enabled (debug.mpsafenet=0). >> >> When it happens, the process doing the copying ends up in "nfsaio" state >> according to ps. Any accesses to the locked mount by other processes >> ends up waiting forever in state "nfs". I have multiple file systems >> mounted from the same server, and only the mount where the data is being >> moved locks up. The others continue to work as expected. >> >> Server: UP, 6-CURRENT from 2005.01.11.05.00.00, if_vr (POLLING) Client: >> SMP (dual AMD MP), 6-CURRENT from 2005.01.11.05.00.00, if_em >> >> The machines are connected with a crossover cable. I've tried both >> schedulers (4BSD and ULE) on the client, but it doesn't make any >> difference (server is running 4BSD). PREEMPTION is enabled on both >> server and client. ADAPTIVE_GIANT is enabled on the client. > >If you run with INVARIANTS and WITNESS, does anything useful get printed >out? Does it make a difference if you run the client with a UP kernel? > >If you break to the debugger on the client and server once wedging has >occurred, what does "show lockedvnods" and "show alllocks" show? > >Is there any chance you could attach a second NFS client to the >configuration, wedge the file system from the first client, and then try >the second client and see if it experiences immediate problems? What is meant by 'wedge the file system' ? - aW