From owner-freebsd-stable@FreeBSD.ORG Thu Apr 28 09:15:52 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74401106566C for ; Thu, 28 Apr 2011 09:15:52 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id F39F08FC0C for ; Thu, 28 Apr 2011 09:15:51 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p3S9Fg53095300 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Thu, 28 Apr 2011 12:15:47 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DB9303E.9090305@digsys.bg> Date: Thu, 28 Apr 2011 12:15:42 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.15) Gecko/20110307 Thunderbird/3.1.9 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20110427221554.GB22139@lava.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: correct way to setup gmirror on 7.4? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Apr 2011 09:15:52 -0000 On 28.04.11 01:30, Freddie Cash wrote: > gmirror doesn't touch the start of the disk, but saves it's metadata > in the last sector of the disk, and creates a new GEOM provider that's > one sector shorter. > > GPT stores it's partition table in the first sector of the disk, and > saves a backup copy of it in the last sector of the disk. This looks like layering issue to me. In theory, both gmirror and gpt should work on 'providers'. So if you give an gmirrored provider to gpt it should touch the last sector of the gmirror, but not the last sector of the disk - and not complain. It should not even be able to see the last sector of the real disk. Is this hard to fix? Daniel