From owner-freebsd-fs@FreeBSD.ORG Thu Jun 30 06:54:44 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 12A08106566B for ; Thu, 30 Jun 2011 06:54:44 +0000 (UTC) (envelope-from ktouet@gmail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id A4C6C8FC18 for ; Thu, 30 Jun 2011 06:54:43 +0000 (UTC) Received: by wwe6 with SMTP id 6so1902836wwe.31 for ; Wed, 29 Jun 2011 23:54:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=huAliHFp6usOKvg5hXtoRAAatzzIfQzv3SZKTn6WIho=; b=f1L4deL9GK9kb4CIMAcIBf6bx5GR9wr5MShCewTNLjFPnG1bK5eICThwe4opf+vvY5 uz4j1C1XLuFsRInkqPcHnoN6UYr9UpdlhmXsqBOr0VPu2y3D+wjsgzXTqu61Z2+ndqed kBYrNAcAItSrDpp0vqGOeuy9VwsVguG01wiI8= MIME-Version: 1.0 Received: by 10.217.3.80 with SMTP id q58mr818340wes.53.1309415340120; Wed, 29 Jun 2011 23:29:00 -0700 (PDT) Received: by 10.216.163.148 with HTTP; Wed, 29 Jun 2011 23:29:00 -0700 (PDT) Date: Thu, 30 Jun 2011 00:29:00 -0600 Message-ID: From: Kurt Touet To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: 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 06:54:44 -0000 I have an admittedly odd zfs v28 array configuration under stable/8 r223484: # zpool status storage pool: storage state: ONLINE scan: resilvered 1.21T in 10h50m with 0 errors on Wed Jun 29 23:21:46 2011 config: NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ad14 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad12 ONLINE 0 0 0 ad4 ONLINE 0 0 0 mirror-1 ONLINE 0 0 0 ad20 ONLINE 0 0 0 ad18 ONLINE 0 0 0 This was simply due to the need to expand the size of the original raidz1 only array and constraints within the box. All drives in the box _were_ 1.5TB. I had a drive in the mirror die this week, and I had 2 spare 2TB drives on hand. So, 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). However, after replacing both drives, the array did not expand in size. It still acts as if the mirror contains 1.5TB drives: storage 6.28T 548G raidz1 5.07T 399G mirror 1.21T 150G Is this normal behaviour? It was my understanding that zfs automatically adapted to having additional drive space in vdevs. -kurt