Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 2 Nov 2010 23:06:57 +0100
From:      Pawel Jakub Dawidek <pjd@FreeBSD.org>
To:        Freddie Cash <fjwcash@gmail.com>
Cc:        freebsd-fs@freebsd.org
Subject:   Re: Converting a non-HAST ZFS pool to a HAST pool
Message-ID:  <20101102220657.GC2051@garage.freebsd.pl>
In-Reply-To: <AANLkTiknuYV53NErau%2BfHLX74yLguv0t0Oi_3exK8%2BEp@mail.gmail.com>
References:  <AANLkTin07ZvB%2Bj2sqdi2bSS_4MwEvEcRPgK-0qc%2Brch4@mail.gmail.com> <20101016222833.GA6765@garage.freebsd.pl> <AANLkTiknuYV53NErau%2BfHLX74yLguv0t0Oi_3exK8%2BEp@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--adJ1OR3c6QgCpb/j
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 02, 2010 at 02:52:45PM -0700, Freddie Cash wrote:
> Okay, so converting a non-HAST ZFS setup to a HAST setup using the
> same drives won't work.
>=20
> Any reason that it wouldn't work when replacing the drives with larger on=
es?
>=20
>  - zpool offline poolname label/disk01
>  - physically replace drive
>  - glabel drive as disk01
>  - configure hast to use label/disk01
>  - zpool replace poolname label/drive01 hast/drive01
>=20
> I can't think of any reason why it would fail, since the hast device
> will be twice as large as the non-hast device it's replacing.  But
> thought I'd double-check, just to be safe.  :)

Yes, this should work.

> Granted, doing it this way would required a *long* initial sync, as
> there's currently 18 TB of data in the pool.  And more going in every
> day.  So it might be better to start fresh.

If you mean HAST initial sync, then this should be now improved in
r214284:

	Before this change on first connect between primary and
	secondary we initialize all the data. This is huge waste of time
	and resources if there were no writes yet, as there is no real
	data to synchronize.

	Optimize this by sending "virgin" argument to secondary, which
	gives it a hint that synchronization is not needed.

	In the common case (where noth nodes are configured at the same
	time) instead of synchronizing everything, we don't synchronize
	at all.

The change is not yet merged to stable/8, AFAIR, but this will happen
today or tomorrow.

You still need to wait for ZFS to copy the data over to the new vdev.

--=20
Pawel Jakub Dawidek                       http://www.wheelsystems.com
pjd@FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!

--adJ1OR3c6QgCpb/j
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)

iEYEARECAAYFAkzQi4AACgkQForvXbEpPzSk2gCcDf0SA7iyDVUHV7jnSnQi4fYZ
m10AoL/pad/aTU0PcZ5EhDr+dSzgm6aZ
=Dr3l
-----END PGP SIGNATURE-----

--adJ1OR3c6QgCpb/j--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101102220657.GC2051>