From owner-freebsd-fs@FreeBSD.ORG  Wed Jul 11 22:05:08 2007
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
X-Original-To: fs@freebsd.org
Delivered-To: freebsd-fs@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 5E47F16A421;
	Wed, 11 Jul 2007 22:05:08 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id 4994213C4C3;
	Wed, 11 Jul 2007 22:05:08 +0000 (UTC)
	(envelope-from bright@elvis.mu.org)
Received: by elvis.mu.org (Postfix, from userid 1192)
	id 2EB471A4DA7; Wed, 11 Jul 2007 15:05:08 -0700 (PDT)
Date: Wed, 11 Jul 2007 15:05:08 -0700
From: Alfred Perlstein <alfred@freebsd.org>
To: Robert Watson <rwatson@FreeBSD.org>
Message-ID: <20070711220508.GY45894@elvis.mu.org>
References: <20070711202640.GV45894@elvis.mu.org>
	<20070711223720.C97304@fledge.watson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070711223720.C97304@fledge.watson.org>
User-Agent: Mutt/1.4.2.3i
Cc: current@freebsd.org, fs@freebsd.org
Subject: Re: bgfsck hosed (lockups) in -current?
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2007 22:05:08 -0000

* Robert Watson <rwatson@FreeBSD.org> [070711 14:37] wrote:
> 
> 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?

Of course, nothing comes up that's interesting.

I'll try to reproduce this and give better feedback in the next few
days.

-- 
- Alfred Perlstein