From owner-freebsd-current@FreeBSD.ORG Tue Oct 8 21:14:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 22D77473 for ; Tue, 8 Oct 2013 21:14:43 +0000 (UTC) (envelope-from lidl@pix.net) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::3c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CEA5B22CF for ; Tue, 8 Oct 2013 21:14:42 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id r98LEfGb016499 for ; Tue, 8 Oct 2013 17:14:41 -0400 (EDT) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <525475C0.4050205@pix.net> Date: Tue, 08 Oct 2013 17:14:40 -0400 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: [CFT] Patch to bsdinstall to support root-on-ZFS and GELI References: <52547185.2000009@freebsd.org> In-Reply-To: <52547185.2000009@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Oct 2013 21:14:43 -0000 >>> 5. I think some substantial part of the MBR code will blow up if you are >>> reinitalizing a previously formatted disk (the bsdlabel will be retasted >>> and come back from the dead). >> Will not some combination of "gpart destroy -F" and (insert suggestion) work? > > Yes, that will work just fine. Actually, it will appear to work, and then viciously hurt (substitute more graphic verb for "hurt") you later, if you happen to repartition, and are using a geom-mirror for your swap space. At least if you manage to get your old geom and new geom on the same physical location of the disk. To be safe, you really need to either zero out the space used by geom before destroying the gpart label when it isn't in use, or run: gmirror deactivate NAME provider1 gmirror deactivate NAME provider2 -Kurt