From owner-freebsd-fs@FreeBSD.ORG Fri Aug 16 15:33:50 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id A0ED2B54 for ; Fri, 16 Aug 2013 15:33:50 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B8AB2EC1 for ; Fri, 16 Aug 2013 15:33:49 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [193.68.6.1]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.6/8.14.6) with ESMTP id r7GFXkw3068525 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 18:33:47 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <520E465A.8090701@digsys.bg> Date: Fri, 16 Aug 2013 18:33:46 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130812 Thunderbird/17.0.8 MIME-Version: 1.0 To: Zeus Panchenko Subject: Re: what is the "correct" way to "replicate" mem stick with ZFS on it? References: <82fb7b70d47ad58db2b2f0b803bf5160@users.userve.net> <20130816172428.79629@relay.ibs.dn.ua> <520E36E8.7080306@digsys.bg> <20130816180312.84150@relay.ibs.dn.ua> In-Reply-To: <20130816180312.84150@relay.ibs.dn.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2013 15:33:50 -0000 On 16.08.13 18:03, Zeus Panchenko wrote: > Daniel Kalchev wrote: >> You can do this instead: >> >> 1. Clone your pool A to pool B >> 2. Export/remove pool A >> 3. Export pool B >> 4. Import exported pool B as pool A. > > in this case I need to remember which mem stick has which pool name on > it, am I correct? If you (at the end of the above process) have pool named A on both memsticks, you don't have to remember anything other than the pool name on the sticks is A. If you don't remember the name of the pool, you can always use 'zpool import' to list the names of the exported pools on the drives you just connected. This also implies it is wise to always export ports before disconnecting devices, and thus you should have one more step above: 5. Export pool A > >> You can have two pools with the same name on one system, >> unfortunately. But you can have different pools with the same name on >> the same (or different) system. > > mmm ... sorry? > > what do you mean, please, under "different pools with the same name on > the same system" ... ? > I see the typo in my post. You should read it: You can not have two pools with the same name on one system, unfortunately. The sunning system cannot have two pools with the same name. This is obvious. But you can connect one pool to the system and import it as A, then after exporting that pool, connect another pool to the system and import it as A too. Say one of these pools might be two drive mirror and the other an five drive raidz. Both pools can be imported as A, but not at the same time. Daniel