From owner-freebsd-fs@FreeBSD.ORG Wed Jul 11 20:52:06 2007 Return-Path: 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 4216516A400; Wed, 11 Jul 2007 20:52:06 +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 3440E13C455; Wed, 11 Jul 2007 20:52:06 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id C45D01A4D80; Wed, 11 Jul 2007 13:26:40 -0700 (PDT) Date: Wed, 11 Jul 2007 13:26:40 -0700 From: Alfred Perlstein To: current@freebsd.org, fs@freebsd.org Message-ID: <20070711202640.GV45894@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: bgfsck hosed (lockups) in -current? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jul 2007 20:52:06 -0000 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. -- - Alfred Perlstein