From owner-freebsd-fs@FreeBSD.ORG Wed Dec 23 01:41:54 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 3744C106566C for ; Wed, 23 Dec 2009 01:41:54 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id C151B8FC18 for ; Wed, 23 Dec 2009 01:41:53 +0000 (UTC) Received: by fxm10 with SMTP id 10so3713978fxm.14 for ; Tue, 22 Dec 2009 17:41:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ufcpjyeOSa+CNdHRrrK9wwIbv+Byq3e5F8m4Q5ieeQg=; b=nRo38Uaood4xHWJevPY6gNMzJ61XQH09Lk+6P6c4YU1LFfZcfaNvsDZHS60sgklC3r WJmyr7c4iKS8MZgIdj5UzP5GoDSXXtEtu6SdKr7bYFaWX/uTDw6U9ZebLdM0rnqymTm8 fMpD8Si7LLxLbEDyLcS3AjLDw4E1u2aEHtT7M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wGdPpBYIhELRKOudg3NGqsDNeU5053Y+czAVUSW5UH1CZFNrQDtbN3yQAj68nNmeHr PNQU54/RTNjc0jLxqq/6tCRoVHtRBUsXZLtQ8lq81dNyBnM64hCYavbq0ul+T5iE3/n0 I+CONNKHfXvRoaH8iNKYpG6LaIMj4vmhbu164= MIME-Version: 1.0 Received: by 10.239.168.138 with SMTP id k10mr1179575hbe.100.1261532512687; Tue, 22 Dec 2009 17:41:52 -0800 (PST) In-Reply-To: <4B315320.5050504@quip.cz> References: <048AF210-8B9A-40EF-B970-E8794EC66B2F@gmail.com> <4B315320.5050504@quip.cz> Date: Tue, 22 Dec 2009 20:41:52 -0500 Message-ID: <5da0588e0912221741r48395defnd11e34728d2b7b97@mail.gmail.com> From: Rich To: Miroslav Lachman <000.fbsd@quip.cz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Wed, 23 Dec 2009 01:41:54 -0000 http://kerneltrap.org/mailarchive/freebsd-fs/2009/9/30/6457763 may be useful to you - it's what we did when we got stuck in a resilver loop. I recall being in the same state you're in right now at one point, and getting out of it from there. I think if you apply that patch, you'll be able to cancel the resilver, and then resilver again with the device you'd like to resilver with. - Rich On Tue, Dec 22, 2009 at 6:15 PM, Miroslav Lachman <000.fbsd@quip.cz> wrote: > 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 = (< >> =A01MB) >> 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? =A0I'm >> eventually going to keep expanding each of my drives one megabyte at a >> time >> using gconcat and space on another drive! =A0Very frustrating... > > You can avoid it by partitioning the drives to the well known 'minimal' s= ize > (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 > _______________________________________________ > 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" > --=20 If you are over 80 years old and accompanied by your parents, we will cash your check.