From owner-freebsd-questions@FreeBSD.ORG Sat May 8 17:45:58 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F22F106566C for ; Sat, 8 May 2010 17:45:58 +0000 (UTC) (envelope-from psteele@maxiscale.com) Received: from server505.appriver.com (server505c.appriver.com [98.129.35.7]) by mx1.freebsd.org (Postfix) with ESMTP id 078C98FC19 for ; Sat, 8 May 2010 17:45:56 +0000 (UTC) X-Policy: GLOBAL - maxiscale.com X-Primary: psteele@maxiscale.com X-Note: This Email was scanned by AppRiver SecureTide X-ALLOW: psteele@maxiscale.com ALLOWED X-Virus-Scan: V- X-Note: Spam Tests Failed: X-Country-Path: UNITED STATES->UNITED STATES->UNITED STATES X-Note-Sending-IP: 98.129.23.15 X-Note-Reverse-DNS: smtp.exg5.exghost.com X-Note-WHTLIST: psteele@maxiscale.com X-Note: User Rule Hits: X-Note: Global Rule Hits: G193 G194 G195 G196 G200 G201 G212 G300 X-Note: Encrypt Rule Hits: X-Note: Mail Class: ALLOWEDSENDER X-Note: Headers Injected Received: from [98.129.23.15] (HELO ht02.exg5.exghost.com) by server505.appriver.com (CommuniGate Pro SMTP 5.3.5) with ESMTPS id 41009602 for freebsd-questions@freebsd.org; Sat, 08 May 2010 12:46:03 -0500 Received: from mbx03.exg5.exghost.com ([169.254.1.219]) by ht02.exg5.exghost.com ([98.129.23.15]) with mapi; Sat, 8 May 2010 12:45:55 -0500 From: Peter Steele To: "freebsd-questions@freebsd.org" Date: Sat, 8 May 2010 12:45:54 -0500 Thread-Topic: Can a foreign drive's mirrors be prevented from joining identically named mirrors? Thread-Index: Acru1AraZcHXOOJ8TJu6YoTFqJ/FiQ== Message-ID: <7B9397B189EB6E46A5EE7B4C8A4BB7CB3E33A500@MBX03.exg5.exghost.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Can a foreign drive's mirrors be prevented from joining identically named mirrors? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 May 2010 17:45:58 -0000 Say I have two systems with two hot-swappable drives and have created mirro= rs for root, var, and swap across those two drives on each system. If I tak= e a drive from one system and insert it into the other system, it appears t= hat the mirror providers on that drive automatically insert themselves into= the identically named mirrors on the system where the drive has been inser= ted. What's worse, they may also become recognized as the mirrors with the = most recent data, even though they came from a different system and should = in fact be immediately flagged as dirty and synchronized with the mirrors o= n the receiving system. The only solution we've found is that drives being inserted into an existin= g system should be thoroughly wiped first. The problem with that is we cann= ot be certain a user will follow that guideline. The alternative is to make= sure that the mirrors are uniquely named across all systems. So for exampl= e instead of having mirrors named root, var, and swap, we could name them r= oot-, var-, and swap-, where is a unique ID ba= sed on the MAC address of a given system's Ethernet interface. This is a 10= 0% solution but it would likely solve most of the problems we've encountere= d. My question is whether there is any other way to accomplish this? We do not= want the mirrors on a drive being inserted into another system to automati= cally added to the receiving systems identically named mirrors.