From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 02:06:53 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 EA33B16A4CE; Fri, 20 Aug 2004 02:06:53 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D286643D45; Fri, 20 Aug 2004 02:06:53 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id C54C172DD4; Thu, 19 Aug 2004 19:06:53 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id C05B072DCB; Thu, 19 Aug 2004 19:06:53 -0700 (PDT) Date: Thu, 19 Aug 2004 19:06:53 -0700 (PDT) From: Doug White To: Martin Blapp In-Reply-To: <20040819231936.G95296@cvs.imp.ch> Message-ID: <20040819190555.S66276@carver.gumbysoft.com> References: <20040819165405.D95296@cvs.imp.ch> <200408191107.31678.jhb@FreeBSD.org> <20040819231936.G95296@cvs.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: SMP: Background fsck deadlocks CURRENT and RELENG_5 solid 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, 20 Aug 2004 02:06:54 -0000 On Thu, 19 Aug 2004, Martin Blapp wrote: > > > I'm currently not able to reboot a paniced or unsincedy disk without > > > doing a normal fsck. Just when the background fsck starts, the box > > > locks solid. The load at this time is not significant. > > > > You might have a corrupted fs from earlier panics. Do a full fsck in single > > user mode and keep doing it until you have no errors (i.e., if it fixes > > anything run fsck again in a loop until you get no fixups at all). > > Nope. This happens on two different SMP boxes. If background fsck comes > into play (whatever happened before is not important), the boxes lock. Can't say I 've had problems with this while debugging the IPI hangs. And those are rock solid. Perhaps you're short on disk space on / and the deltas from the snapshot take you over the edge? Or have some sort of large I/O operation run just after boot? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org