From owner-freebsd-current@FreeBSD.ORG  Tue Apr 12 00:42:35 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7718416A4CE
	for <current@freebsd.org>; Tue, 12 Apr 2005 00:42:35 +0000 (GMT)
Received: from obsecurity.dyndns.org
	(CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.111])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E86E43D2D
	for <current@freebsd.org>; Tue, 12 Apr 2005 00:42:35 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id A502A514FE; Mon, 11 Apr 2005 17:42:32 -0700 (PDT)
Date: Mon, 11 Apr 2005 17:42:32 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: Dan Nelson <dnelson@allantgroup.com>
Message-ID: <20050412004232.GA83769@xor.obsecurity.org>
References: <20050411234512.GA23344@xor.obsecurity.org>
	<20050412003114.GD284@dan.emsphone.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw"
Content-Disposition: inline
In-Reply-To: <20050412003114.GD284@dan.emsphone.com>
User-Agent: Mutt/1.4.2.1i
cc: current@freebsd.org
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: Softupdates not preventing lengthy fsck
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2005 00:42:35 -0000


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

On Mon, Apr 11, 2005 at 07:31:15PM -0500, Dan Nelson wrote:
> In the last episode (Apr 11), Kris Kennaway said:
> > I'm seeing the following problem: on 6.0 machines which have had a lot
> > of FS activity in the past but are currently quiet, an unclean reboot
> > will require an hour or more of fscking and will end up clearing
> > thousands of inodes:
>=20
> This might be expected behaviour if the previous boot tried to do a
> bgfsck and failed.  It should set a flag forcing a full fsck on the
> next boot, which will clear out the half-committed inodes from the
> previous crash.  I see it often on 5.*.

I should have mentioned that I have background_fsck=3DNO (because of too
many filesystem corruption problems after panics).  The previous time
the system booted it also had to fsck, and did the same thing (it's
now been running for >2 hours).

Kris

--GvXjxJ+pjyke8COw
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCWxl3Wry0BWjoQKURAsEyAKCgT+m+hohnXEfCghUFCK7qOhZpgQCglLxJ
nmDdMC0WoKR1ifCVmUw/hl8=
=Nb0Q
-----END PGP SIGNATURE-----

--GvXjxJ+pjyke8COw--