From owner-freebsd-current@FreeBSD.ORG  Mon Apr 11 23:45:16 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 3E38A16A4CE
	for <current@FreeBSD.org>; Mon, 11 Apr 2005 23:45:16 +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 E75A343D55
	for <current@FreeBSD.org>; Mon, 11 Apr 2005 23:45:15 +0000 (GMT)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id 3921951326; Mon, 11 Apr 2005 16:45:12 -0700 (PDT)
Date: Mon, 11 Apr 2005 16:45:12 -0700
From: Kris Kennaway <kris@obsecurity.org>
To: current@FreeBSD.org
Message-ID: <20050411234512.GA23344@xor.obsecurity.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="W/nzBZO5zC0uMSeA"
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: 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: Mon, 11 Apr 2005 23:45:16 -0000


--W/nzBZO5zC0uMSeA
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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:

[...]
/dev/da0s1e: UNREF FILE I=269731  OWNER=root MODE=100644
/dev/da0s1e: SIZE=8555 MTIME=Apr 18 02:29 2002  (CLEARED)
/dev/da0s1e: UNREF FILE I=269732  OWNER=root MODE=100644
/dev/da0s1e: SIZE=3281 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269733  OWNER=root MODE=100644
/dev/da0s1e: SIZE=4252 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269734  OWNER=root MODE=100644
/dev/da0s1e: SIZE=4252 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269735  OWNER=root MODE=100644
/dev/da0s1e: SIZE=4252 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269736  OWNER=root MODE=100644
/dev/da0s1e: SIZE=1346 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269737  OWNER=root MODE=100644
/dev/da0s1e: SIZE=7573 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269738  OWNER=root MODE=100644
/dev/da0s1e: SIZE=7272 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269739  OWNER=root MODE=100644
/dev/da0s1e: SIZE=4076 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269740  OWNER=root MODE=100644
/dev/da0s1e: SIZE=20471 MTIME=Mar 18 07:48 2000  (CLEARED)
/dev/da0s1e: UNREF FILE I=269741  OWNER=root MODE=100644
[...]

It's as if dirty buffers aren't being written out properly, or
something.  Has anyone else seen this?

Kris

--W/nzBZO5zC0uMSeA
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFCWwwIWry0BWjoQKURAu3BAJ4tTB/+yuamDywhpNeapzi3+yVcGwCgzU1G
dsIeCcdaqszvMde0k4SdSbw=
=OSm4
-----END PGP SIGNATURE-----

--W/nzBZO5zC0uMSeA--