bgfsck hosed (lockups) in -current?

[Kostik Belousov]

On Wed, Jul 11, 2007 at 03:05:08PM -0700, Alfred Perlstein wrote:
> * Robert Watson <rwatson at 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.
Please. Deadlock debugging chapter from dev handbook contains enumeration
of the needed things.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070712/4b2cedcf/attachment.pgp