From owner-freebsd-fs@FreeBSD.ORG Wed Apr 27 18:55:18 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 81AA1106566B for ; Wed, 27 Apr 2011 18:55:18 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1D2038FC08 for ; Wed, 27 Apr 2011 18:55:18 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:4ee:2016:db72:ee7c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 18C6D4AC2D; Wed, 27 Apr 2011 22:55:16 +0400 (MSD) Date: Wed, 27 Apr 2011 22:55:11 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <669365808.20110427225511@serebryakov.spb.ru> To: Miroslav Lachman <000.fbsd@quip.cz> In-Reply-To: <4DB81F90.6020108@quip.cz> References: <20110427101728.49C801065709@hub.freebsd.org> <4DB7F61C.8060003@digsys.bg> <4DB81F90.6020108@quip.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable 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 Reply-To: lev@FreeBSD.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Apr 2011 18:55:18 -0000 Hello, Miroslav. You wrote 27 =E0=EF=F0=E5=EB=FF 2011 =E3., 17:52:16: >> 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=20 > partitions available on device /dev/ada0 and /dev/mirror/gm0 so there=20 > will be two devices promoting same labels! I don't know the order of=20 > tasting devices, but there is a chance that system will boot (mount root > by label) from broken ada0 instead of gm0. Even without broken mirror, in case of perfectly valid reboot, glabel could pick-up label first (before gmirror) from one of (both are non-broken) mirror components, and after that gmirror builds itself from one true component (ada0, for example) and one label-provided (instead of ada1) :( So, UFS labels CAN NOT BE MIXED with gmirror... --=20 // Black Lion AKA Lev Serebryakov