From owner-freebsd-questions@freebsd.org  Tue Feb 28 10:33:33 2017
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2EB2FCF07E8
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Tue, 28 Feb 2017 10:33:33 +0000 (UTC)
 (envelope-from jmc-freebsd2@milibyte.co.uk)
Received: from queue01c.mail.zen.net.uk (queue01c.mail.zen.net.uk
 [212.23.3.237]) by mx1.freebsd.org (Postfix) with ESMTP id E0A1A7AE
 for <freebsd-questions@freebsd.org>; Tue, 28 Feb 2017 10:33:32 +0000 (UTC)
 (envelope-from jmc-freebsd2@milibyte.co.uk)
Received: from [212.23.1.23] (helo=smarthost03d.mail.zen.net.uk)
 by queue01c.mail.zen.net.uk with esmtp (Exim 4.72)
 (envelope-from <jmc-freebsd2@milibyte.co.uk>) id 1cieTJ-00056z-Hp
 for freebsd-questions@freebsd.org; Tue, 28 Feb 2017 09:53:29 +0000
Received: from [82.71.56.121] (helo=curlew.milibyte.co.uk)
 by smarthost03d.mail.zen.net.uk with esmtps
 (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80)
 (envelope-from <jmc-freebsd2@milibyte.co.uk>)
 id 1cieTD-0003OP-4X; Tue, 28 Feb 2017 09:53:23 +0000
Received: from [192.168.1.13] (helo=curlew)
 by curlew.milibyte.co.uk with esmtp (Exim 4.88)
 (envelope-from <jmc-freebsd2@milibyte.co.uk>)
 id 1cieTa-0000sK-94; Tue, 28 Feb 2017 09:53:46 +0000
Date: Tue, 28 Feb 2017 09:53:46 +0000
From: Mike Clarke <jmc-freebsd2@milibyte.co.uk>
Cc: Motty Cruz <motty.cruz@gmail.com>, freeBSD Mailing List
 <freebsd-questions@freebsd.org>
Message-ID: <20170228095346.759e12f1@curlew>
In-Reply-To: <CADqw_gJNN4sRSbg0An_DTHj-4PEkb-p49d+9iNT0V3EwytXckw@mail.gmail.com>
References: <58b49669.d264620a.7d458.47f0@mx.google.com>
 <CADqw_gJNN4sRSbg0An_DTHj-4PEkb-p49d+9iNT0V3EwytXckw@mail.gmail.com>
X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.29; amd64-portbld-freebsd11.0)
MIME-Version: 1.0
X-SA-Exim-Connect-IP: 192.168.1.13
X-SA-Exim-Mail-From: jmc-freebsd2@milibyte.co.uk
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on curlew.lan
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 MISSING_HEADERS autolearn=no autolearn_force=no version=3.4.1
Subject: Re: how to expand zpool
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on curlew.milibyte.co.uk)
X-Originating-smarthost03d-IP: [82.71.56.121]
Feedback-ID: 82.71.56.121
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 10:33:33 -0000

On Tue, 28 Feb 2017 08:27:10 +0100
Michael Schuster <michaelsprivate@gmail.com> wrote:

> simply put, physically replace one disk, 'zpool replace' it. when that's
> done, next disk ... This process is very well documented :-)

You need to set autoexpand for the pool to "on" before it can grow to
utilise the extra space.

Also see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216881
there's a bug which causes zpool detach to hang if autoexpand is set to
"on". I don't know if this also affects zpool replace but to be safe
leave autoexpand set to "off" until after you've replaced the last
drive.

-- 
Mike Clarke