From owner-freebsd-stable@FreeBSD.ORG  Tue Jul 20 10:04:22 2010
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5DD621065676
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 2010 10:04:22 +0000 (UTC)
	(envelope-from ptyll@nitronet.pl)
Received: from mail.nitronet.pl (pop3.nitronet.pl [195.90.106.28])
	by mx1.freebsd.org (Postfix) with ESMTP id C49938FC19
	for <freebsd-stable@freebsd.org>; Tue, 20 Jul 2010 10:04:21 +0000 (UTC)
Received: from mailnull by mail.nitronet.pl with virscan (Exim 4.72 (FreeBSD))
	(envelope-from <ptyll@nitronet.pl>) id 1Ob9Qg-000IaW-7H
	for freebsd-stable@freebsd.org; Tue, 20 Jul 2010 11:48:02 +0200
Date: Tue, 20 Jul 2010 11:47:54 +0200
From: Pawel Tyll <ptyll@nitronet.pl>
X-Priority: 3 (Normal)
Message-ID: <426290558.20100720114754@nitronet.pl>
To: Andriy Gapon <avg@icyb.net.ua>
In-Reply-To: <4C45612A.2060502@icyb.net.ua>
References: <AANLkTimOrwHe7xiwoap2H2mUtA7vU6TjENkPC4yJ02_z@mail.gmail.com>
	<AANLkTimOIgCIO4txpPeeoMrRSYAqM25V7cm-h7djmZUC@mail.gmail.com>
	<AANLkTikPOgIqkm3GhIsEnvuvEHvlc44cnh6GJQ1k7Ja_@mail.gmail.com>
	<AANLkTimgi2Btzv9krZZPHCPiyCcwtQyF72BmRzA1kuvi@mail.gmail.com>
	<AANLkTinm-kYD2vwTBCh49AeU0oxuPSOPXjusMa3FGk1h@mail.gmail.com>
	<AANLkTikPJDoiTUwNHVtTDiFMdFkm6v6_ra8JYkuChBJC@mail.gmail.com>
	<AANLkTikCCmGmIcRpj7gjnRBEfLE40IjOmelMYu9WkSUO@mail.gmail.com>
	<4C44B104.2050000@libeljournal.com>
	<AANLkTinnAxJxARcJrDgYxnpql2n2a_6bQc7fSuZLAzuF@mail.gmail.com>
	<4C45612A.2060502@icyb.net.ua>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Scanned: Nitronet.pl
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: ptyll@nitronet.pl
X-SA-Exim-Scanned: No (on mail.nitronet.pl); SAEximRunCond expanded to false
Cc: freebsd-stable <freebsd-stable@freebsd.org>,
	Garrett Moore <garrettmoore@gmail.com>
Subject: Re: Problems replacing failing drive in ZFS pool
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jul 2010 10:04:22 -0000

Hi guys,

> I second what others have said - crap.
> But there could be some hope, not sure.
> Can you check what is the actual size used by the pool on the disk?
> It should be somewhere in zdb -C output ("asize"?).
> If I remember correctly, that actual size should be a multiple of some ra=
ther
> large power of two, so it could be that it is smaller than 'User Capacity=
' of both
> old and new drives.
Well, I see some possibilities for creative solution here, using some
ssd (or usb stick or mdconfig as act of desperation) and gconcat, but
it's asking for trouble and should probably be considered a temporary
hack.

What I personally would do is get a 2TB drive and use it instead, with
gpt and -l for label, and replace it as gpt/something. Using 100 or so
MB less than whole disk is also a good idea, as you can see ;)

Cheers and good luck.