From owner-freebsd-fs@FreeBSD.ORG Tue Dec 22 23:15:49 2009 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 D64C41065692 for ; Tue, 22 Dec 2009 23:15:49 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) by mx1.freebsd.org (Postfix) with ESMTP id 948CA8FC27 for ; Tue, 22 Dec 2009 23:15:49 +0000 (UTC) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 7F58619E046; Wed, 23 Dec 2009 00:15:47 +0100 (CET) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 2716919E045; Wed, 23 Dec 2009 00:15:45 +0100 (CET) Message-ID: <4B315320.5050504@quip.cz> Date: Wed, 23 Dec 2009 00:15:44 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.6) Gecko/20091206 SeaMonkey/2.0.1 MIME-Version: 1.0 To: Steven Schlansker References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> In-Reply-To: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: ZFS: Can't repair raidz2 (Cannot replace a replacing device) 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, 22 Dec 2009 23:15:49 -0000 Steven Schlansker wrote: > As a corollary, you may notice some funky concat business going on. > This is because I have drives which are very slightly different in size (< 1MB) > and whenever one of them goes down and I bring the pool up, it helpfully (?) > expands the pool by a whole megabyte then won't let the drive back in. > This is extremely frustrating... is there any way to fix that? I'm > eventually going to keep expanding each of my drives one megabyte at a time > using gconcat and space on another drive! Very frustrating... You can avoid it by partitioning the drives to the well known 'minimal' size (size of smallest disk) and use the partition instead of raw disk. For example ad12s1 instead of ad12 (if you creat slices by fdisk) of ad12p1 (if you creat partitions by gpart) You can also use labels instead of device name. Miroslav Lachman