From owner-freebsd-current@FreeBSD.ORG Tue Oct 12 21:49:46 2004 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 8F34F16A4CE; Tue, 12 Oct 2004 21:49:46 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B09543D41; Tue, 12 Oct 2004 21:49:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 633F251385; Tue, 12 Oct 2004 14:52:10 -0700 (PDT) Date: Tue, 12 Oct 2004 14:52:10 -0700 From: Kris Kennaway To: Scott Long Message-ID: <20041012215210.GA78176@xor.obsecurity.org> References: <416AE7D7.3030502@murex.com> <200410112038.i9BKcCWt051290@apollo.backplane.com> <416C1B10.7030103@murex.com> <200410121818.i9CIIGRx092072@apollo.backplane.com> <20041012205105.GA76130@xor.obsecurity.org> <416C50C8.9010903@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <416C50C8.9010903@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: Mikhail Teterin cc: freebsd-current@freebsd.org cc: bde@zeta.org.au cc: Kris Kennaway Subject: Re: panic in ffs (Re: hangs in nbufkv) 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 Oct 2004 21:49:46 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 12, 2004 at 03:46:48PM -0600, Scott Long wrote: > >FYI, I ran the package build cluster with 4:1 ratios for a few months > >and did not have problems. If there are major bugs there I would have > >expected to come across them. > > > >Kris >=20 > IIRC, the fragment allocation code in FFS allocates in terms of bits=20 > withing a byte, so anything that is 8:1 or less should work. So I should try 16:1, or is that guaranteed to fail? Kris --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBbFIJWry0BWjoQKURAkPqAJ4g52yj+sTXwJ+jK3qWPomeNpFoNgCghIHs l5v89XDuBhv1L6Gh+pjGe+Y= =gzS7 -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx--