From owner-freebsd-current@FreeBSD.ORG Tue Apr 12 22:15:49 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 56BFE16A4CE; Tue, 12 Apr 2005 22:15:49 +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 1140443D2D; Tue, 12 Apr 2005 22:15:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8B506530EE; Tue, 12 Apr 2005 15:15:47 -0700 (PDT) Date: Tue, 12 Apr 2005 15:15:47 -0700 From: Kris Kennaway To: Don Lewis Message-ID: <20050412221546.GB65915@xor.obsecurity.org> References: <425BE215.4090406@samsco.org> <200504121951.j3CJpCCY036689@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VrqPEDrXMn8OVzN4" Content-Disposition: inline In-Reply-To: <200504121951.j3CJpCCY036689@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 22:15:49 -0000 --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 12, 2005 at 12:51:12PM -0700, Don Lewis wrote: > On 12 Apr, Scott Long wrote: > > Kris Kennaway wrote: >=20 > >> 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) > >>=20 > >> Kris > >=20 > > Don might not know that your workload involves creating and deleting > > full ports/ trees repeatedly, and those trees contain hundreds of > > tousands of inodes each. >=20 > I suspected that, especially given the inode timestamps in the partial > transcript. Actually the ports trees are not recreated (they're mounted via nullfs and accessed read-only), and the files that are created are due to building, installing and uninstalling of ports on a plain old ufs2. It's still a lot of files though. > > If there is a reference count leak and those > > deletions aren't ever being finalized, then there would be a whole lot > > of work for fsck to do =3D-) Might also explain why disks have been > > unexpectedly filling up on package machines (like mine). >=20 > Sounds likely. When the disk starts looking unexpectedly full, can you > unmount the file system or does the attempt fail with and EBUSY error? > What happens if you fsck the file system after it has been unmounted? > Are snapshots being used? Scott was the one who tried to repair the system after this happened, so he can probably answer it better. I'm certainly not using snapshots myself. Kris --VrqPEDrXMn8OVzN4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCXEiRWry0BWjoQKURAhjcAKCetahLDM7F7CzixeqfiCIv9y6XuACdHH0O v0BuzOt28SZVkeHF605xXBE= =ZiXP -----END PGP SIGNATURE----- --VrqPEDrXMn8OVzN4--