From owner-freebsd-geom@FreeBSD.ORG  Wed Apr 21 12:56:27 2010
Return-Path: <owner-freebsd-geom@FreeBSD.ORG>
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 A50E51065672;
	Wed, 21 Apr 2010 12:56:27 +0000 (UTC)
	(envelope-from bu7cher@yandex.ru)
Received: from forward2.mail.yandex.net (forward2.mail.yandex.net [77.88.46.7])
	by mx1.freebsd.org (Postfix) with ESMTP id 511AC8FC1B;
	Wed, 21 Apr 2010 12:56:27 +0000 (UTC)
Received: from smtp2.mail.yandex.net (smtp2.mail.yandex.net [77.88.46.102])
	by forward2.mail.yandex.net (Yandex) with ESMTP id 7C44738A8FF2;
	Wed, 21 Apr 2010 16:56:25 +0400 (MSD)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1271854585; bh=Vq1ufzHWapoOXjv2+pScrjbhwBNJbFNgdDEQ51Dlriw=;
	h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References:
	In-Reply-To:Content-Type:Content-Transfer-Encoding;
	b=DcUVDC3WmT/yb/Z4JMVUefOj0bH+aeQrwtp6FFacd1dWZXEoho8DDplwNQzqR8K5I
	/nD5LSv2erSJysqpmdmjE8Iu1kNxyI1v7chZLp1ASrN3TCvSlI/R5kT3q6iEPfj3fi
	ac43wiA5lf6wxdL8whb5D5c0870XcCF5pG3IFcGs=
Received: from [127.0.0.1] (ns.kirov.so-ups.ru [77.72.136.145])
	by smtp2.mail.yandex.net (Yandex) with ESMTPSA id 1B9A3528067;
	Wed, 21 Apr 2010 16:56:25 +0400 (MSD)
Message-ID: <4BCEF5F8.6090102@yandex.ru>
Date: Wed, 21 Apr 2010 16:56:24 +0400
From: "Andrey V. Elsukov" <bu7cher@yandex.ru>
User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231)
MIME-Version: 1.0
To: Andriy Gapon <avg@icyb.net.ua>
References: <B814515407B5445092FD63116EA3DA6B@neo>	<4BCEE9E2.6010007@yandex.ru>
	<4BCEEC66.1080804@yandex.ru> <4BCEEF06.8010203@icyb.net.ua>
In-Reply-To: <4BCEEF06.8010203@icyb.net.ua>
Content-Type: text/plain; charset=KOI8-R; format=flowed
Content-Transfer-Encoding: 7bit
X-Yandex-TimeMark: 1271854585
X-Yandex-Spam: 1
X-Yandex-Front: smtp2.mail.yandex.net
Cc: Lister <lister@kawashti.org>, Marcel Moolenaar <marcel@FreeBSD.org>,
	freebsd-geom@FreeBSD.org
Subject: Re: OCE and GPT
X-BeenThere: freebsd-geom@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: GEOM-specific discussions and implementations
	<freebsd-geom.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-geom>
List-Post: <mailto:freebsd-geom@freebsd.org>
List-Help: <mailto:freebsd-geom-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-geom>,
	<mailto:freebsd-geom-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2010 12:56:27 -0000

On 21.04.2010 16:26, Andriy Gapon wrote:
> will your patch take care of moving the second copy of GPT towards (new) disk end
> if disk size is increased?

Current implementation of resize feature is targeted to resize
providers withing scheme. But with GPT we have problem, after
booting with bigger media size the second partition table will
be lost. And GPT will be broken. I think first of it should be recovered.
And there are some plans about implementing this feature.
After that partitions within scheme can be resized with my patch.

Recovering of GPT will write secondary table and also should fix internal
information about media size. And there can be several ways (if we think about
generic implementation). What should we do when media size will be smaller that
it was before? Should we reject this way of recovering and allow recovering
only for the same size or bigger media size?

-- 
WBR, Andrey V. Elsukov