Date: Thu, 14 Aug 2014 12:02:54 +0100 From: krad <kraduk@gmail.com> To: "Mike." <the.lists@mgm51.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: zpool from 32bit os to 64bit os Message-ID: <CALfReycwh2ZZ_ry0GG1-erwvcA%2BvP2dRGS7L2UZhxRM%2BKYaYFw@mail.gmail.com> In-Reply-To: <201408121123120262.00AFDB15@smtp.24cl.home> References: <53E92013.2020206@chroot.pl> <FF8E51982DE10ACDF7ED1C5A@192.168.1.50> <CALfReye9HDGyTWSGkR_BJmss_n%2BXX0UPacuK9L7pLR9K2-MAoA@mail.gmail.com> <53E9C0D0.1080206@chroot.pl> <D6AFB1BF-46D9-4BED-B407-97BE614417C5@kraus-haus.org> <201408121123120262.00AFDB15@smtp.24cl.home>
next in thread | previous in thread | raw e-mail | index | archive | help
if the pool is a mirror, you can just split it, move one or one set of the drives across and try to import it. One all is good move the other disks across then attach them after cleaning them On 12 August 2014 16:23, Mike. <the.lists@mgm51.com> wrote: > On 8/12/2014 at 9:43 AM Paul Kraus wrote: > > |On Aug 12, 2014, at 3:22, Lukasz <lukasz@chroot.pl> 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=E2=80=99t > |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 <zpool name || ID>` 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=E2=80=99ve > |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 > > > > > _______________________________________________ > 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALfReycwh2ZZ_ry0GG1-erwvcA%2BvP2dRGS7L2UZhxRM%2BKYaYFw>