From owner-freebsd-arch@FreeBSD.ORG Sun Sep 11 16:50:49 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E473816A420; Sun, 11 Sep 2005 16:50:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 760E343D49; Sun, 11 Sep 2005 16:50:49 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.3/8.13.3) with ESMTP id j8BGofJT058130; Sun, 11 Sep 2005 10:50:42 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <43246066.8070709@samsco.org> Date: Sun, 11 Sep 2005 10:50:46 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <760.1126453829@phk.freebsd.dk> In-Reply-To: <760.1126453829@phk.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Jung-uk Kim , freebsd-arch@freebsd.org Subject: Re: Bigger boot block size? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2005 16:50:50 -0000 Poul-Henning Kamp wrote: > In message <86y863k70q.fsf@xps.des.no>, =?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?= > writes: > > >>We also need to fix gstripe, gmirror etc. so they place their metadata >>at the start of the provider instead of at the end. > > > There are perfectly good arguments for metadata at front and metadata > at the end and none of the arguments is definitive. > > In GEOM it is a private matter for the classes in question, and as > long as they handle it properly, I have no issues with any placement > of metadata. > There are actually very good arguments for putting the metadata at the end of the components. Consider that it means that you can boot a gmirror array without system BIOS support. Scott