From owner-freebsd-current@FreeBSD.ORG Thu Aug 19 21:20:56 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 6E87916A4CE; Thu, 19 Aug 2004 21:20:56 +0000 (GMT) Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EE9543D39; Thu, 19 Aug 2004 21:20:55 +0000 (GMT) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id i7JLKnZG050349; Thu, 19 Aug 2004 23:20:50 +0200 (CEST) (envelope-from Martin.Blapp@imp.ch) Date: Thu, 19 Aug 2004 23:20:49 +0200 (CEST) From: Martin Blapp To: John Baldwin In-Reply-To: <200408191107.31678.jhb@FreeBSD.org> Message-ID: <20040819231936.G95296@cvs.imp.ch> References: <20040819165405.D95296@cvs.imp.ch> <200408191107.31678.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checksum: a750e214d8dd751c7e87460e084d827a X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0020 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="0.5247 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.44 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: Thu, 19 Aug 2004 21:20:56 -0000 Hi. > > 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. Please try yourself ! Martin