From owner-freebsd-current@FreeBSD.ORG  Wed Jul 11 21:37:55 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 23DAC16A41F;
	Wed, 11 Jul 2007 21:37:55 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42])
	by mx1.freebsd.org (Postfix) with ESMTP id D08A813C480;
	Wed, 11 Jul 2007 21:37:54 +0000 (UTC)
	(envelope-from rwatson@FreeBSD.org)
Received: from fledge.watson.org (fledge.watson.org [209.31.154.41])
	by cyrus.watson.org (Postfix) with ESMTP id 3B1FF47CA4;
	Wed, 11 Jul 2007 17:37:54 -0400 (EDT)
Date: Wed, 11 Jul 2007 22:37:54 +0100 (BST)
From: Robert Watson <rwatson@FreeBSD.org>
X-X-Sender: robert@fledge.watson.org
To: Alfred Perlstein <alfred@freebsd.org>
In-Reply-To: <20070711202640.GV45894@elvis.mu.org>
Message-ID: <20070711223720.C97304@fledge.watson.org>
References: <20070711202640.GV45894@elvis.mu.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: current@freebsd.org, fs@freebsd.org
Subject: Re: bgfsck hosed (lockups) in -current?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2007 21:37:55 -0000


On Wed, 11 Jul 2007, Alfred Perlstein wrote:

> I have current as of last week.
>
> I noticed that if I needed a bgfsck on ufs when rebooting my system would 
> lock up almost immediately.  Everything would deadlock.
>
> If I rebooted single user and did a regular "fsck -y" then continued to 
> boot, I'd be OK.
>
> Has anyone else experienced this?  I'm going to update to the most recent 
> current and get more information (which wait channels etc) but wanted to 
> know if anyone knew about this.
>
> I recall seeing a LOT of fixes for various deadlocks in snapshots and bgfsck 
> going in lately, but nothing that looked to me as if it'd trigger a 
> regression.

I'm not seeing this either -- have you tried running a manual fsck to see if 
it turns up anything deeply unsatisfying that could be causing bgfsck some 
bother?

Robert N M Watson
Computer Laboratory
University of Cambridge