From owner-freebsd-fs@FreeBSD.ORG Wed Apr 27 14:08:52 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3FF11065677 for ; Wed, 27 Apr 2011 14:08:52 +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 72FDF8FC17 for ; Wed, 27 Apr 2011 14:08:52 +0000 (UTC) Received: from elsa.codelab.cz (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 6771B19E02E; Wed, 27 Apr 2011 15:52:19 +0200 (CEST) Received: from [192.168.1.2] (ip-86-49-61-235.net.upcbroadband.cz [86.49.61.235]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9D4FC19E02D; Wed, 27 Apr 2011 15:52:17 +0200 (CEST) Message-ID: <4DB81F90.6020108@quip.cz> Date: Wed, 27 Apr 2011 15:52:16 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.18) Gecko/20110320 SeaMonkey/2.0.13 MIME-Version: 1.0 To: Daniel Kalchev References: <20110427101728.49C801065709@hub.freebsd.org> <4DB7F61C.8060003@digsys.bg> In-Reply-To: <4DB7F61C.8060003@digsys.bg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Why not just name the cam-ata devices the same as the old, names? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 14:08:52 -0000 Daniel Kalchev wrote: [...] > What should be done, ideally before the 9.0 release is to find some sane > resolution method of what happens when you happen to have two (for > example) 'root' UFS labels during boot/mount time. ...and that's the problem with labels in case of gmirror. When you create gm0 of ada0 and ada1, then sometime in the future ada0 timedout and is dropped by gmirror, on next reboot you will have same partitions available on device /dev/ada0 and /dev/mirror/gm0 so there will be two devices promoting same labels! I don't know the order of tasting devices, but there is a chance that system will boot (mount root by label) from broken ada0 instead of gm0. That's why I am staying away from labels on gmirrored disk. (I am using labels on USB flash disks or USB external drives) Miroslav Lachman