From owner-freebsd-questions@FreeBSD.ORG Tue Aug 12 15:23:19 2014 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4BC70A2F for ; Tue, 12 Aug 2014 15:23:19 +0000 (UTC) Received: from oneyou.mcmli.com (oneyou.mcmli.com [IPv6:2001:470:1d:8da::100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "oneyou.mcmli.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EC1E2EAC for ; Tue, 12 Aug 2014 15:23:19 +0000 (UTC) Received: from sentry.24cl.com (unknown [IPv6:2001:558:6017:a2:a860:3073:4c46:6ac9]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "sentry.24cl.com", Issuer "Mike's Certificate Authority" (verified OK)) by oneyou.mcmli.com (Postfix) with ESMTPS id 3hXd903YZdz1DN4 for ; Tue, 12 Aug 2014 11:23:16 -0400 (EDT) Received: from BigBloat (bigbloat.24cl.home [10.20.1.4]) by sentry.24cl.com (Postfix) with ESMTP id 3hXd8z3M6Bz1BrL for ; Tue, 12 Aug 2014 11:23:15 -0400 (EDT) Message-ID: <201408121123120262.00AFDB15@smtp.24cl.home> In-Reply-To: References: <53E92013.2020206@chroot.pl> <53E9C0D0.1080206@chroot.pl> X-Mailer: Courier 3.50.00.09.1098 (http://www.rosecitysoftware.com) (P) Date: Tue, 12 Aug 2014 11:23:12 -0400 From: "Mike." To: freebsd-questions@FreeBSD.org Subject: Re: zpool from 32bit os to 64bit os Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Aug 2014 15:23:19 -0000 On 8/12/2014 at 9:43 AM Paul Kraus wrote: |On Aug 12, 2014, at 3:22, Lukasz wrote: | |> Thank you for answers. I'll try with export/import... I hope my data |> will be safe during this operation. :) | |If you want your data to be really, really safe, then: 0. Make at least one backup of the data before doing anything else, and make sure the backup worked. | |1. Make sure to export from the original server. While you *can* force the |import on the new server, I really, really hate using the force option as |the check you are overriding is there for a reason. Sometimes you don=92t |have a choice, but this is not a Disaster Recovery situation (and you do |not want it to become one). | |2. When you run the initial `zpool import` on the new system it will list |the zpools it finds *and* their state. If the zpool is not complete or is |any way not clean, then DO NOT IMPORT it and put the drives back in the |old system and figure out what is wrong there. | |3. When you run the `zpool import ` also set the |readonly property using the -o option. This way if there is some kind of |incompatibility (and ZFS does check for this and should want you, but it |never really hurts to be paranoid) the new system will not write anything |to the zpool. | |4. If the readonly import goes well and all the data is there and looks |good, then export the zpool and import it again without the readonly |property and you should be all set. | |The above may be overkill (depending on what your data is worth :-), but I |have seen bugs in ZFS (although not very many in the past few years, I=92ve |been using ZFS since about 2007) and the additional time can save you lots |of time in recovery later on. | |-- |Paul Kraus |paul@kraus-haus.org | |_______________________________________________ |freebsd-questions@freebsd.org mailing list |http://lists.freebsd.org/mailman/listinfo/freebsd-questions |To unsubscribe, send any mail to |"freebsd-questions-unsubscribe@freebsd.org" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D