Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Jul 2007 11:42:40 +0300
From:      Kostik Belousov <kostikbel@gmail.com>
To:        Alfred Perlstein <alfred@freebsd.org>
Cc:        Robert Watson <rwatson@freebsd.org>, current@freebsd.org, fs@freebsd.org
Subject:   Re: bgfsck hosed (lockups) in -current?
Message-ID:  <20070712084240.GB2200@deviant.kiev.zoral.com.ua>
In-Reply-To: <20070711220508.GY45894@elvis.mu.org>
References:  <20070711202640.GV45894@elvis.mu.org> <20070711223720.C97304@fledge.watson.org> <20070711220508.GY45894@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--XPTkPaWipqgB+utH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jul 11, 2007 at 03:05:08PM -0700, Alfred Perlstein wrote:
> * Robert Watson <rwatson@FreeBSD.org> [070711 14:37] wrote:
> >=20
> > On Wed, 11 Jul 2007, Alfred Perlstein wrote:
> >=20
> > >I have current as of last week.
> > >
> > >I noticed that if I needed a bgfsck on ufs when rebooting my system wo=
uld=20
> > >lock up almost immediately.  Everything would deadlock.
> > >
> > >If I rebooted single user and did a regular "fsck -y" then continued t=
o=20
> > >boot, I'd be OK.
> > >
> > >Has anyone else experienced this?  I'm going to update to the most rec=
ent=20
> > >current and get more information (which wait channels etc) but wanted =
to=20
> > >know if anyone knew about this.
> > >
> > >I recall seeing a LOT of fixes for various deadlocks in snapshots and=
=20
> > >bgfsck going in lately, but nothing that looked to me as if it'd trigg=
er a=20
> > >regression.
> >=20
> > I'm not seeing this either -- have you tried running a manual fsck to s=
ee=20
> > if it turns up anything deeply unsatisfying that could be causing bgfsc=
k=20
> > some bother?
>=20
> Of course, nothing comes up that's interesting.
>=20
> 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.

--XPTkPaWipqgB+utH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (FreeBSD)

iD8DBQFGlel/C3+MBN1Mb4gRAt1vAKDBMQRWJB1T/YomwXl7VXo1Wj25mQCeLRB8
WksXrTP5X2bqmVVhv6k93uU=
=kGEQ
-----END PGP SIGNATURE-----

--XPTkPaWipqgB+utH--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070712084240.GB2200>