From owner-freebsd-stable@FreeBSD.ORG Fri Feb 17 17:10:15 2012 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 C321E10656A9 for ; Fri, 17 Feb 2012 17:10:15 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6BB908FC1B for ; Fri, 17 Feb 2012 17:09:59 +0000 (UTC) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id E3DE528426; Fri, 17 Feb 2012 18:09:56 +0100 (CET) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id AADF628424; Fri, 17 Feb 2012 18:09:55 +0100 (CET) Message-ID: <4F3E89E3.3060608@quip.cz> Date: Fri, 17 Feb 2012 18:09:55 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.19) Gecko/20110420 Lightning/1.0b1 SeaMonkey/2.0.14 MIME-Version: 1.0 To: Pete French References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: wblock@wonkity.com, freebsd-stable@freebsd.org, mandrews@bit0.com, freebsd@jdc.parodius.com Subject: Re: New BSD Installer 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: Fri, 17 Feb 2012 17:10:15 -0000 Pete French wrote: >> I wasn't aware you could do that. I was only aware that it was the >> other way around. That (my) misconception seems to also be relayed >> by others such as Miroslav who said: > > Should this not be the recommended way of doing things even for MBR > disks ? I have a lot of machines booting from gmirror, but we always > do it by mirroring MBR partitions (or GPT ones). I cant see why you would > want to do it the other way round in fact. It doesnt gain you anything > does it ? Yes it does? Am I the only one person on the whole earth seeing the big difference in easy setup of mirroring two drives instead of many individual partitions? Freddie Cash already write about disk thrashing on rebuild after power failure, but initial setup or repair after disk replacement is also pain with mirroring individual partitions. > As someone else pointed out, you do need to partition the two drives > to match, and add bootloaders to them. But thats not really a great > hardship is it, and everything just works properly. You dont need > any different bootloader (as it sees the start of the drive and the > gmirror stuff is at the end). > Comparing our usual setup with 7 partitions after disk failure and replacement: Mirroring whole drives (after failed disk replacement): 1) gmirror forget -v gm0 2) gmirror insert -v gm0 ada1 And I am done! Mirroring individual partitions (maintenance nightmare)): 1) find sizes of partitions 2) create partitions on new drive 3) install boot sector 4) gmirror forget -v gm0p1 5) gmirror insert -v gm0p1 ada1p1 (and wait til synchronized) 6) gmirror forget -v gm0p2 7) gmirror insert -v gm0p2 ada1p2 (and wait til synchronized) 8) gmirror forget -v gm0p3 9) gmirror insert -v gm0p3 ada1p3 (and wait til synchronized) 10) gmirror forget -v gm0p4 11) gmirror insert -v gm0p4 ada1p4 (and wait til synchronized) 12) gmirror forget -v gm0p5 13) gmirror insert -v gm0p5 ada1p5 (and wait til synchronized) 14) gmirror forget -v gm0p6 15) gmirror insert -v gm0p6 ada1p6 (and wait til synchronized) 16) gmirror forget -v gm0p7 17) gmirror insert -v gm0p7 ada1p7 And after 15 more steps, you are done too. I think you cannot compare mirrored partitions to what can be done by ZFS mirror or gmirror on whole drives and I am not willing to go by this way. I will use gmirror and MBR where possible. Miroslav Lachman