From owner-freebsd-arch@FreeBSD.ORG Tue Dec 2 00:05:40 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5D511065672 for ; Tue, 2 Dec 2008 00:05:40 +0000 (UTC) (envelope-from peter@wemm.org) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.173]) by mx1.freebsd.org (Postfix) with ESMTP id 8B6D38FC08 for ; Tue, 2 Dec 2008 00:05:40 +0000 (UTC) (envelope-from peter@wemm.org) Received: by wf-out-1314.google.com with SMTP id 24so2933802wfg.7 for ; Mon, 01 Dec 2008 16:05:39 -0800 (PST) Received: by 10.142.84.3 with SMTP id h3mr4695379wfb.149.1228176339603; Mon, 01 Dec 2008 16:05:39 -0800 (PST) Received: by 10.142.255.21 with HTTP; Mon, 1 Dec 2008 16:05:39 -0800 (PST) Message-ID: Date: Mon, 1 Dec 2008 16:05:39 -0800 From: "Peter Wemm" To: "Marcel Moolenaar" In-Reply-To: <68B9D78C-C0CF-4D64-AF53-C3736EEC8D23@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <57809A37-B81C-4F50-A418-CD9303F06B72@mac.com> <0F1745AA-611F-40B2-85F3-32FD78BC4B58@mac.com> <68B9D78C-C0CF-4D64-AF53-C3736EEC8D23@mac.com> Cc: FreeBSD Arch Subject: Re: RFC: making gpart default 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: Tue, 02 Dec 2008 00:05:40 -0000 On Sat, Nov 29, 2008 at 7:30 PM, Marcel Moolenaar wrote: > > On Nov 29, 2008, at 1:56 PM, Peter Wemm wrote: [..] >> * There should be some guidance or hints on laying out disks. For >> example, a gpart create -s gpt on a raid volume ends up with a start >> sector of 34 for the free space. There should be a documentation hint >> to round up start sectors to a power of 2 and/or block size on a raid. >> eg: if you have a raid with 64K stripes, then move the start sector >> from 34 to 128. Otherwise we end up with file systems issuing >> transactions that can split across multiple raid stripes. FWIW, I >> conveniently filled this hole with boot code. > > Hmmm... gpart(8) typically can't store this kind > of information on-disk, but other than that it > supports alignment/padding already. We just need > a way to tell gpart about it. Maybe this should > come from the provider (i.e. underlying geom)... I was more thinking of a man page note to warn of the issue. Also, in the gpt case, it might make sense in gpt partition table case to round up the initial size to a power of 2. Right now we lose 34 sectors from the beginning. Rounding it to 64 total at least gets us to an even power of 2. UFS's frequent block size of 16K shouldn't cross any underlying stripe boundaries in the usual case. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell