Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Apr 2005 11:26:38 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Bill Moran <wmoran@potentialtech.com>
Cc:        Kris Kennaway <kris@obsecurity.org>
Subject:   Re: background_fsck=no does not work?
Message-ID:  <20050425182638.GD40370@xor.obsecurity.org>
In-Reply-To: <20050425141900.363bca66.wmoran@potentialtech.com>
References:  <DD8197BD35BCC63A18AF62CB@palle.girgensohn.se> <426BA8FA.3080602@samsco.org> <426BAAE4.1040606@incubus.de> <17005.12955.757773.350868@roam.psg.com> <20050425181329.GA41455@xor.obsecurity.org> <20050425141900.363bca66.wmoran@potentialtech.com>

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

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

On Mon, Apr 25, 2005 at 02:19:00PM -0400, Bill Moran wrote:
> Kris Kennaway <kris@obsecurity.org> wrote:
>=20
> > On Mon, Apr 25, 2005 at 08:10:35AM -1000, Randy Bush wrote:
> > > >> not always be clean.  Softupdates (hopefully) means that it will be
> > > >> consistent and recoverable, but what you're seeing here is normal =
and
> > > > Why "hopefully"?  Aren't people convinced that it works correctly?
> > >=20
> > > i am convinced, but some of the hosts seem not to be :-)
> > >=20
> > > i see shutdowns which 0 0 0 0 and then shut, and when restarted
> > > single user and fscked manually show errors.  though i think this
> > > may be in current, which is on most of my hosts.
> >=20
> > Yeah, others have reported this problem on -current, but 5.x does not
> > have it.
>=20
> Actually, I have seen a similar problem on 5.x WRT OpenOffice ...
> 0. OpenOffice hangs and cant' be killed
> 1. Reboot system
> 2. System claims all buffers flushed, then just hangs
> 3. After hardbooting, filesystems need fscked
>=20
> I noticed others with similar complaints about OpenOffice, so I haven't
> said much.  The problem also happens pretty rarely, and I don't have any
> idea how to reproduce it on demand.

What's needed to move forward on this is for someone to break to DDB
when this happens and obtain a trace of the blocked process (and
preferably a crashdump).  See the developers' handbook for more
information.

Kris

--lc9FT7cWel8HagAv
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCbTZeWry0BWjoQKURAt0NAJ0aTM3MYDw4kiNV3EYXr1AIBYHzWQCgj8o9
2hSM3RdNWxXCdGDhE1qlt34=
=Zi9b
-----END PGP SIGNATURE-----

--lc9FT7cWel8HagAv--



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