From owner-freebsd-fs@FreeBSD.ORG Tue Nov 2 21:52:46 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2149106564A; Tue, 2 Nov 2010 21:52:46 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 68F958FC08; Tue, 2 Nov 2010 21:52:46 +0000 (UTC) Received: by gwj16 with SMTP id 16so252898gwj.13 for ; Tue, 02 Nov 2010 14:52:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=9QYKjd2uod7lsxVBjQP0IhlOal77FKpB0gA+dbdQtRU=; b=euUXKh5FXoTXVUynedn/5BVfFe8BIC70fghoA7B4dzhQxDtx3NC1dZYikvdVBBKu3o P147M83IGlhGif6M9Oeu69BSViLq2Uh4BcN/KXcVydYUG5uu/ltZ+OY/eoi9+AZ+633V 5nn5xwwf8hKIwU+abISlzx2n9fmBfm+fOSgso= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Iy/Zw9bhmfeiHrvMKOwTLUyQNW6KCLA6MSo7v1AIM45PIb+jbaLc/Vn3WWR+K2FA5I SmnIR5R9NgCS+nT8B1BEqkCKfRfgC4+H2Jd5IKbfh3g4ZoxB3OFfPu3Le5tu2NwVXoV9 88t9/auWjODaZE6bOeH/HY4+dqHl/V41ALCnw= MIME-Version: 1.0 Received: by 10.91.24.17 with SMTP id b17mr2025646agj.192.1288734765442; Tue, 02 Nov 2010 14:52:45 -0700 (PDT) Received: by 10.90.97.7 with HTTP; Tue, 2 Nov 2010 14:52:45 -0700 (PDT) In-Reply-To: <20101016222833.GA6765@garage.freebsd.pl> References: <20101016222833.GA6765@garage.freebsd.pl> Date: Tue, 2 Nov 2010 14:52:45 -0700 Message-ID: From: Freddie Cash To: Pawel Jakub Dawidek Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Converting a non-HAST ZFS pool to a HAST pool X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2010 21:52:46 -0000 On Sat, Oct 16, 2010 at 3:28 PM, Pawel Jakub Dawidek wrot= e: > On Fri, Oct 15, 2010 at 11:37:34AM -0700, Freddie Cash wrote: >> Has anyone looked into, attempted, or considered converting a non-HAST >> ZFS pool configuration into a HAST one? =C2=A0While the pool is live and >> the server is in use. =C2=A0Would it even be possible? >> >> For example, would the following work (in a pool with a single raidz2 >> vdev, where the underlying GEOM provider is glabel) >> =C2=A0 - zpool offline 1 drive =C2=A0(pool is now running degraded) >> =C2=A0 - configure hastd in master mode with a single provider using the >> "offline" disk (hast metadata takes the place of glabel metadata) > > HAST metadata takes much more space than glabel metadata. The latter > takes only one sector, while the former depends on provider size, but we > have to keep entire extent bitmap there, so definitely more than one > sector. Okay, so converting a non-HAST ZFS setup to a HAST setup using the same drives won't work. Any reason that it wouldn't work when replacing the drives with larger ones= ? - 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 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. :) 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. --=20 Freddie Cash fjwcash@gmail.com