Re: bgfsck hosed (lockups) in -current?
- From: Kostik Belousov <kostikbel@xxxxxxxxx>
- Date: Thu, 12 Jul 2007 11:42:40 +0300
On Wed, Jul 11, 2007 at 03:05:08PM -0700, Alfred Perlstein wrote:
* Robert Watson <rwatson@xxxxxxxxxxx> [070711 14:37] wrote:Please. Deadlock debugging chapter from dev handbook contains enumeration
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.
of the needed things.
Attachment:
pgpFWxSMcIP3c.pgp
Description: PGP signature
- References:
- bgfsck hosed (lockups) in -current?
- From: Alfred Perlstein
- Re: bgfsck hosed (lockups) in -current?
- From: Robert Watson
- Re: bgfsck hosed (lockups) in -current?
- From: Alfred Perlstein
- bgfsck hosed (lockups) in -current?
- Prev by Date: Re: Oddity with an(4): Channel reported by ifconfig is wrong
- Next by Date: Re: Debugging times
- Previous by thread: Re: bgfsck hosed (lockups) in -current?
- Next by thread: [patch] suspend problems
- Index(es):
Relevant Pages
|