From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 15:34:06 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 C069F16A4CF for ; Thu, 19 Aug 2004 15:34:06 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B93443D45 for ; Thu, 19 Aug 2004 15:34:06 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 9471 invoked from network); 19 Aug 2004 15:34:06 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Aug 2004 15:34:05 -0000 Received: from [10.50.40.208] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i7JFY2aJ055630; Thu, 19 Aug 2004 11:34:02 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Thu, 19 Aug 2004 11:07:31 -0400 User-Agent: KMail/1.6.2 References: <20040819165405.D95296@cvs.imp.ch> In-Reply-To: <20040819165405.D95296@cvs.imp.ch> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408191107.31678.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Martin Blapp 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: Thu, 19 Aug 2004 15:34:06 -0000 On Thursday 19 August 2004 10:58 am, Martin Blapp wrote: > Hi all, > > 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). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org