From owner-svn-src-all@freebsd.org Tue Mar 28 18:20:28 2017 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19DF5D2287E; Tue, 28 Mar 2017 18:20:28 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id D6DFC7A7; Tue, 28 Mar 2017 18:20:26 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id A8702273C2; Tue, 28 Mar 2017 18:20:19 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id v2SIKGur069050; Tue, 28 Mar 2017 18:20:16 GMT (envelope-from phk@phk.freebsd.dk) To: rgrimes@freebsd.org, "Rodney W. Grimes" cc: Bruce Evans , Julian Elischer , Warner Losh , src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r316064 - head/sys/boot/i386/boot2 In-reply-to: <201703281555.v2SFtoSU005538@pdx.rh.CN85.dnsmgr.net> From: "Poul-Henning Kamp" References: <201703281555.v2SFtoSU005538@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <69048.1490725215.1@critter.freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Tue, 28 Mar 2017 18:20:16 +0000 Message-ID: <69049.1490725216@critter.freebsd.dk> X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Mar 2017 18:20:28 -0000 -------- In message <201703281555.v2SFtoSU005538@pdx.rh.CN85.dnsmgr.net>, "Rodney W= . Gri mes" writes: >I think we still have an 8k size limit on boot1 for ffs/(ufs1 or ufs2) Having a former release-engineer & disk-I/O renovator on the UFS2 team took care of that: We tried to be future compatible, and UFS2 will look four different places for the superblock: +64k, +8k, +0k and +256k, (the latter named SBLOCK_PIGGY because somebody senior thought even 64k was an outrageous waste of space :-) -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .