From owner-freebsd-fs@FreeBSD.ORG Thu Jun 30 07:03:59 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 80EBE1065675 for ; Thu, 30 Jun 2011 07:03:59 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 192E28FC0C for ; Thu, 30 Jun 2011 07:03:58 +0000 (UTC) Received: by wyg24 with SMTP id 24so1830333wyg.13 for ; Thu, 30 Jun 2011 00:03:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=olCK2GKj7gwTLEEcZk6HFDkkBET2ZxKfFMe6VFJxFTI=; b=qJ1Hu4yYk35z3Z1CVPunEpd8pJqGYG0pAMP3jNz4EzgyaNIOqBMgiOWSXaucv44LAs 5nA1QMvvW0mpF4TbYbQ1Q2TD8t6sTv3HlK34VnetJOD3EFxFGSS0z7oxWy+QmW4dSjGg 7Mq53rlDslNCTiZrOeksjcaOUItmhYM+M+HiA= MIME-Version: 1.0 Received: by 10.216.139.37 with SMTP id b37mr2432733wej.41.1309417437762; Thu, 30 Jun 2011 00:03:57 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.216.135.169 with HTTP; Thu, 30 Jun 2011 00:03:57 -0700 (PDT) In-Reply-To: References: Date: Thu, 30 Jun 2011 00:03:57 -0700 X-Google-Sender-Auth: ycmNHEK4zyloMV3iGYygoSnqhH8 Message-ID: From: Artem Belevich To: Kurt Touet Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: ZFS v28 array doesn't expand with larger disks in 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: Thu, 30 Jun 2011 07:03:59 -0000 On Wed, Jun 29, 2011 at 11:29 PM, Kurt Touet wrote: > I have an admittedly odd zfs v28 array configuration under stable/8 r2234= 84: > > # zpool status storage > =A0pool: storage > =A0state: ONLINE > =A0scan: resilvered 1.21T in 10h50m with 0 errors on Wed Jun 29 23:21:46 = 2011 > config: > > =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0storage =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0raidz1-0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0ad14 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0 =A0ad6 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0 =A0ad12 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0 =A0ad4 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0mirror-1 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0ad20 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > =A0 =A0 =A0 =A0 =A0 =A0ad18 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > > This was simply due to the need to expand the size of the original > raidz1 only array and constraints within the box. =A0All drives in the > box _were_ 1.5TB. =A0I had a drive in the mirror die this week, and I > had 2 spare 2TB drives on hand. =A0So, I decided to replace both of the > 1.5TB drives in the array with 2TB drives (and free up a little more > space on the box). =A0However, after replacing both drives, the array > did not expand in size. =A0It still acts as if the mirror contains 1.5TB > drives: > > storage =A0 =A0 6.28T =A0 548G > =A0raidz1 =A0 =A05.07T =A0 399G > =A0mirror =A0 =A01.21T =A0 150G > > Is this normal behaviour? =A0It was my understanding that zfs > automatically adapted to having additional drive space in vdevs. You still have to set 'autoexpand' property on the pool in order for expansion to happen. Perevious versions would expand the pool on re-import or on boot. --Artem > > -kurt > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" >