From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 19:51:23 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 144DD37B401; Wed, 2 Jul 2003 19:51:23 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B656244001; Wed, 2 Jul 2003 19:51:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.9/8.12.9) with ESMTP id h632p8aQ019387; Wed, 2 Jul 2003 19:51:08 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.9/8.12.9/Submit) id h632p0SM019386; Wed, 2 Jul 2003 19:51:00 -0700 (PDT) Date: Wed, 2 Jul 2003 19:50:59 -0700 From: "David O'Brien" To: "Alan L. Cox" Message-ID: <20030703025059.GB18897@dragon.nuxi.com> Mail-Followup-To: David O'Brien , "Alan L. Cox" , Peter Holm , current@freebsd.org, alc@freebsd.org, Eirik Oeverby References: <20030630125553.GA90064@peter.osted.lan> <20030630135037.GA90436@peter.osted.lan> <3F009DCE.6A69BB24@imimic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F009DCE.6A69BB24@imimic.com> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.1-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: alc@freebsd.org cc: current@freebsd.org cc: Eirik Oeverby Subject: Re: Disk/FS I/O issues in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jul 2003 02:51:23 -0000 On Mon, Jun 30, 2003 at 03:30:06PM -0500, Alan L. Cox wrote: > I've been able to reproduce what I believe is the problem. (In my case, > I reset my machine and watched the background fsck slowly grind to a > halt. Foreground fsck is fine.) > > The problem actually appears to be in vm_page_alloc(), not > vm_pageout.c. Look for a commit to resolve this in a few hours. Has this been committed. I *so* ran into this yesterday (3 times) with a 70gb /usr and a June 30th kernel. -- -- David (obrien@FreeBSD.org)