From owner-freebsd-stable@FreeBSD.ORG Thu Aug 8 18:23:42 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 505F3EE1; Thu, 8 Aug 2013 18:23:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward3l.mail.yandex.net (forward3l.mail.yandex.net [IPv6:2a02:6b8:0:1819::3]) by mx1.freebsd.org (Postfix) with ESMTP id 0AF782A33; Thu, 8 Aug 2013 18:23:42 +0000 (UTC) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17]) by forward3l.mail.yandex.net (Yandex) with ESMTP id 708561501492; Thu, 8 Aug 2013 22:23:39 +0400 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id ED59919000ED; Thu, 8 Aug 2013 22:23:38 +0400 (MSK) Received: from v10-164-213.yandex.net (v10-164-213.yandex.net [84.201.164.213]) by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTP id hpQPP4jqv6-NcUidYpV; Thu, 8 Aug 2013 22:23:38 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1375986218; bh=o7kzUyqXjgqRJY0vFhErc3QdGr5xbiTBJdsrG3hq6i8=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type: Content-Transfer-Encoding; b=Unlx1srno7clgmm+WaaoJmkjh/q0XreNhEvPCYFrazzVPidfQGEyI75y777sQIP4H JMAuQzx14x+a/eqgRa0mXIyLRLuSYE4tqUim5FDj4T3tuF8wf7tbKRwSa4F2SpuK+y +IbBsDYnGw2eNH2+R002fnH8qJFixOzVC2AKmMwE= Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.ru Message-ID: <5203E153.4070605@yandex.ru> Date: Thu, 08 Aug 2013 22:20:03 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Peter Wemm Subject: Re: Problem with zfsloader on 9.2-BETA2 References: <51FD5709.7050306@FreeBSD.org> <5200C7A3.3070403@yandex.ru> <5202006B.5060708@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: J David , freebsd-stable@freebsd.org, Andriy Gapon X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Aug 2013 18:23:42 -0000 On 08.08.2013 01:46, Peter Wemm wrote: > I've run into this before. Our loader and kernel are excessively > pedantic about this. > > gpart create -s gpt -n ... > > leads to bootblocks or loader or kernel rejecting it if it is < 128, > and some of the bootblocks reject it if it is > 128. > > As things stand, the -n option is basically "make my system unusable". The minimum number of GPT partitions that gpart(8) can create is 128. It seems it's not fully correct now. The spec only requires that at least 16k must be reserved for GPT table, but this doesn't mean that all 16kbytes should be used, also gpt table entry can be greater than 128 bytes in future. gptboot uses static buffer to load GPT, and its size is 16k. So, if you create GPT with more than 128 entries, it won't boot. -- WBR, Andrey V. Elsukov