From owner-freebsd-fs@FreeBSD.ORG Tue Sep 20 00:50:51 2011 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 8C4DE106564A for ; Tue, 20 Sep 2011 00:50:51 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by mx1.freebsd.org (Postfix) with ESMTP id 3C47A8FC12 for ; Tue, 20 Sep 2011 00:50:50 +0000 (UTC) Received: by vws5 with SMTP id 5so14728vws.17 for ; Mon, 19 Sep 2011 17:50:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=XZMTXRJgfT+4/x0VAVKMfeOTXW1wYDnL6DHGt2bg+vQ=; b=c/ZHAr7zOcAsT1//2pVtlscgBSet3ITV2abmMGiwC76ALEb3Tg4Bv5xTbGs//Rig4E yO7oeqzrlEalpPkW8ddBT3Kfz0d+EbuBmw0ABE+2Nb/yLQiFNNXdLueUXX5tDApDfWBY s0S5kQ4d046OSoxug/TJ1PxvQermeFvoXVZd4= MIME-Version: 1.0 Received: by 10.220.154.201 with SMTP id p9mr38459vcw.2.1316479850183; Mon, 19 Sep 2011 17:50:50 -0700 (PDT) Received: by 10.220.198.130 with HTTP; Mon, 19 Sep 2011 17:50:50 -0700 (PDT) Received: by 10.220.198.130 with HTTP; Mon, 19 Sep 2011 17:50:50 -0700 (PDT) In-Reply-To: <20110919233045.GA71606@icarus.home.lan> References: <9774D03B-A8C7-48DE-9BC4-528DD4134787@altesco.nl> <20110919213813.GA70527@icarus.home.lan> <20110919233045.GA71606@icarus.home.lan> Date: Mon, 19 Sep 2011 17:50:50 -0700 Message-ID: From: Freddie Cash To: Jeremy Chadwick Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS auto expand mirror 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, 20 Sep 2011 00:50:51 -0000 Once all of the disks in the vdev have been replaced, making them all the same size. Doesn't matter in what order they are replaced. Freddie fjwcash@gmail.com On Sep 19, 2011 4:30 PM, "Jeremy Chadwick" wrote: > On Mon, Sep 19, 2011 at 02:54:06PM -0700, Freddie Cash wrote: >> On Mon, Sep 19, 2011 at 2:38 PM, Jeremy Chadwick >> wrote: >> >> > On Mon, Sep 19, 2011 at 10:49:56AM -0700, Freddie Cash wrote: >> > > On Mon, Sep 19, 2011 at 10:08 AM, Ben Stuyts wrote: >> > > >> > > > I want to expand an existing mirror by replacing the existing drives >> > with >> > > > bigger ones. This is on: >> > > > FreeBSD xxx 7.3-STABLE FreeBSD 7.3-STABLE #2: Mon Sep 20 18:36:08 CEST >> > 2010 >> > > > root@xxx:/usr/obj/usr/src/sys/xxx amd64 >> > > > >> > > > # zpool status home >> > > > pool: home >> > > > state: ONLINE >> > > > scrub: scrub completed after 2h0m with 0 errors on Mon Sep 19 18:25:45 >> > > > 2011 >> > > > config: >> > > > >> > > > NAME STATE READ WRITE CKSUM >> > > > home ONLINE 0 0 0 >> > > > mirror ONLINE 0 0 0 >> > > > ad5s1a ONLINE 0 0 0 >> > > > ad7s1a ONLINE 0 0 0 >> > > > >> > > > Will this version of FreeBSD auto-expand to the new, bigger drive size >> > once >> > > > they are both replaced? I did not see the autoexpand property in this >> > pool. >> > > > zpool is v13, zfs is v3. >> > > > >> > > >> > > No. You will need to reboot the system in order for the extra space to >> > > become usable in the pool. Or, if none of the OS is installed on the >> > pool, >> > > you can export/import the pool to make the new space available. >> > >> > Does this advice/fact apply to FreeBSD 7.3? To my knowledge it does >> > not. The ZFS version is too old. >> >> It's worked for me on our storage servers. These started with ZFSv6 and >> have been upgraded through each version, currently running ZFSv28 on >> 8-STABLE. >> >> Early versions of ZFS need the reboot or export/import cycle. Newer >> versions pick up the new space as soon as the resilver of the last drive in >> the vdev occurs (if the autoexpand property is enabled on the pool). > > I was about to ask what the autoexpand property was for then, but you've > answered it in your 2nd paragraph here. > > Also, need some clarification here: when you say "the last drive in the > vdev" do you effectively mean "once all the drives in the vdev are of > the same size", or do you quite literally mean "the last device/disk > shown in the vdev"? > > I can't imagine the latter being correct but I want clarification for > myself as well as others who read this. Thanks! > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, US | > | Making life hard for others since 1977. PGP 4BD6C0CB | >