From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 14:41:18 2005 Return-Path: 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 3189A16A4CF; Tue, 12 Apr 2005 14:41:18 +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 E282443D5A; Tue, 12 Apr 2005 14:41:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 29D5C5125F; Tue, 12 Apr 2005 07:41:17 -0700 (PDT) Date: Tue, 12 Apr 2005 07:41:17 -0700 From: Kris Kennaway To: Don Lewis Message-ID: <20050412144116.GA39174@xor.obsecurity.org> References: <20050412035111.GA31366@xor.obsecurity.org> <200504121201.j3CC1nZ1035643@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <200504121201.j3CC1nZ1035643@gw.catspoiler.org> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Apr 2005 14:41:18 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 12, 2005 at 05:01:49AM -0700, Don Lewis wrote: > On 11 Apr, Kris Kennaway wrote: > > On Mon, Apr 11, 2005 at 06:43:17PM -0700, Don Lewis wrote: > >> On 11 Apr, Kris Kennaway wrote: > >> > I'm seeing the following problem: on 6.0 machines which have had a l= ot > >> > 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 > >> > [...] > >> > /dev/da0s1e: UNREF FILE I=3D269731 OWNER=3Droot MODE=3D100644 > >> > /dev/da0s1e: SIZE=3D8555 MTIME=3DApr 18 02:29 2002 (CLEARED) > >>=20 > >> > /dev/da0s1e: UNREF FILE I=3D269741 OWNER=3Droot MODE=3D100644 > >> > [...] > >> >=20 > >> > It's as if dirty buffers aren't being written out properly, or > >> > something. Has anyone else seen this? > >>=20 > >> This looks a lot like it could be a vnode refcnt leak. Files won't get > >> removed from the disk while they are still in use (the old unlink while > >> open trick). Could nullfs be a factor? > >=20 > > Yes, I make extensive use of read-only nullfs. > >=20 > > Kris (fsck still running) >=20 > It would also be interesting to find out why fsck is taking so long to > run. I don't see anything obvious in the code. I can take a transcript of the entire fsck next time if you like :-) (it ran for more than 5 hours on the 24G drive and was still going after I went to bed) Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCW94MWry0BWjoQKURAtIXAJ46XC8vUmBlFkh9CcuE2lYpr+B7nwCdFLpS zGrf0Nw5VPIA3Sm7XYEE1yU= =DJRf -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo--