From owner-freebsd-stable@FreeBSD.ORG Mon Jul 19 22:28:58 2010 Return-Path: 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 C6422106564A for ; Mon, 19 Jul 2010 22:28:58 +0000 (UTC) (envelope-from garrettmoore@gmail.com) Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 83FFC8FC16 for ; Mon, 19 Jul 2010 22:28:58 +0000 (UTC) Received: by iwn35 with SMTP id 35so6398659iwn.13 for ; Mon, 19 Jul 2010 15:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=Ba57ewnje8TzsReIDYa5YDqk+zdBhudGl9w61u7dUwg=; b=OnQKnXed9t5ydwtZauzwDxqJqFCvGd5F2HqWNzBfx+ZPUOnbQgynEOJD9WzIaNqmDo Pin82N/SLLOJ0b6k32KtVHN7QA10TqEauDx4TtioQ8JDA9Lf3LSoceGcOSndGE1DlQyg rSQ8o1FM8/9Fov5848dk8PBcZ0W/XL4Mxz5fk= 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; b=d0N2yELpPGvOd8Avlt5q0TEDv2LZOq8lyLpHSU68sJdF5fg6OTQ4fuQRzg4prHhNsh xe3qC+LwSMycR04unM+G76/D2ztLcGUV7/E/PlQ+HoT4n1rHlNS+PC9qMFfTsjYqpius rSiHdOmuH2eP4BG9C360q8xH3mY2K1qIQm3s0= MIME-Version: 1.0 Received: by 10.231.14.194 with SMTP id h2mr6153503iba.67.1279578496593; Mon, 19 Jul 2010 15:28:16 -0700 (PDT) Received: by 10.231.117.72 with HTTP; Mon, 19 Jul 2010 15:28:16 -0700 (PDT) In-Reply-To: References: <4C44B104.2050000@libeljournal.com> Date: Mon, 19 Jul 2010 18:28:16 -0400 Message-ID: From: Garrett Moore To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable , John Hawkes-Reed 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Jul 2010 22:28:58 -0000 Well thank you very much Western Digital for your absolutely pathetic RMA service sending me an inferior drive. I'll call tomorrow and see what can be done; I'm going to insist on these 00R6B0 drives being sent back, and being given a drive of >= 1,500,301,910,016 bytes capacity. At least now I learned how to hotswap :/ On Mon, Jul 19, 2010 at 6:22 PM, Adam Vande More wrote: > > > On Mon, Jul 19, 2010 at 5:04 PM, Garrett Moore wrote: > >> Well, hotswapping worked, but now I have a totally different problem. Just >> for reference: >> # zpool offline tank da3 >> # camcontrol stop da3 >> >> # camcontrol rescan all >> <'da3 lost device, removing device entry'> >> # camcontrol rescan all >> <'da3 at mpt0 ...', so new drive was found! yay> >> # zpool replace tank da3 >> *cannot replace da3 with da3: device is too small* >> >> So I looked at the smartctl output for the old and new drive. Old: >> Device Model: WDC WD15EADS-00P8B0 >> Serial Number: WD-WMAVU0087717 >> Firmware Version: 01.00A01 >> User Capacity: 1,500,301,910,016 bytes >> >> New: >> Device Model: WDC WD15EADS-00R6B0 >> Serial Number: WD-WCAVY4770428 >> Firmware Version: 01.00A01 >> User Capacity: 1,500,300,828,160 bytes >> >> God damnit, Western Digital. What can I do now? It's such a small >> difference, is there a way I can work around this? > > > Uff da, I'm pretty sure the answer is no, you would have had to use the > smallest device first when creating the pool I think. > > >> My other replacement >> drive is the "00R6B0" drive model as well, with the slightly smaller >> capacity. >> > > > > -- > Adam Vande More >