From owner-freebsd-geom@FreeBSD.ORG Mon May 23 17:43:40 2011 Return-Path: Delivered-To: freebsd-geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9EDC1065675; Mon, 23 May 2011 17:43:40 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 834568FC1F; Mon, 23 May 2011 17:43:40 +0000 (UTC) Received: from [10.30.101.53] ([209.117.142.2]) (authenticated bits=0) by harmony.bsdimp.com (8.14.4/8.14.3) with ESMTP id p4NHe1LG004826 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES128-SHA bits=128 verify=NO); Mon, 23 May 2011 11:40:03 -0600 (MDT) (envelope-from imp@bsdimp.com) Mime-Version: 1.0 (Apple Message framework v1084) From: Warner Losh In-Reply-To: <4DDA9046.8050902@yandex.ru> Date: Mon, 23 May 2011 11:39:54 -0600 Message-Id: References: <4DDA2F0B.2040203@yandex.ru> <6DF62987-141B-4BB3-8E8D-9966EBAC828B@bsdimp.com> <4DDA9046.8050902@yandex.ru> To: "Andrey V. Elsukov" X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (harmony.bsdimp.com [10.0.0.6]); Mon, 23 May 2011 11:40:04 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Marcel Moolenaar , Poul-Henning Kamp , freebsd-geom@freebsd.org Subject: Re: [RFC] Remove requirement of alignment to track from MBR scheme X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 May 2011 17:43:41 -0000 On May 23, 2011, at 10:50 AM, Andrey V. Elsukov wrote: >=20 >> In any event, I'd be tempted to use a #define for 4096 like >> MBR_MAX_SECTOR_SIZE. >>=20 >> - msize =3D MIN(pp->mediasize / pp->sectorsize, UINT32_MAX); >> + msize =3D MIN(pp->mediasize / pp->sectorsize, 2 * UINT32_MAX); >>=20 >> Why this change? I think that it is in two places. >=20 > Currently we have limit to msize =3D UINT32_MAX, but partition in MBR = has > start offset and size (not end offset). Theoretically it can have size > that is up to UINT32_MAX sectors, also start offset can be UINT32_MAX. > And for example, for 4T disk we can have 2 partitions with 2TB size. Are there any extant examples of this? The CW is that the maximum size = for an MBR device is 2TB. Warner=