From owner-freebsd-stable@FreeBSD.ORG Tue Jul 20 01:25:44 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 AB3E71065675 for ; Tue, 20 Jul 2010 01:25:44 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing03.lava.net (outgoing03.lava.net [IPv6:2001:1888:0:1:202:b3ff:fe1d:6b98]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3428FC1A for ; Tue, 20 Jul 2010 01:25:44 +0000 (UTC) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing03.lava.net (Postfix) with ESMTP id A20091019C; Mon, 19 Jul 2010 15:25:43 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 44FD4196E48; Mon, 19 Jul 2010 15:25:43 -1000 (HST) Date: Mon, 19 Jul 2010 15:25:43 -1000 From: Clifton Royston To: Garrett Moore Message-ID: <20100720012542.GA25848@lava.net> Mail-Followup-To: Garrett Moore , freebsd-stable References: <4C44B104.2050000@libeljournal.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable 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: Tue, 20 Jul 2010 01:25:44 -0000 On Mon, Jul 19, 2010 at 06:28:16PM -0400, Garrett Moore wrote: > 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 :/ This is the wrong time to find it out, I know, but: For geom mirror purposes I have taken to carving out HD partitions which are exactly a round number of GiB, and at least 100 MiB less than the claimed capacity. I then label the partitions using geom label, and use the partition label specification in setting up the mirror. The first means that when an unannounced change in drive capacity like this happens, I can still add the smaller drive into a RAID set of larger drives painlessly, because the partition sizes will still match exactly. (It also means that if I can only find a larger drive, e.g. if 1TB drives later drop off the market or are more expensive than larger drives, I can easily add a larger drive into the set by making its partition size match the rest.) The second means that if the BIOS/probing sequence does its little dance and the drives end up getting renumbered, it does not affect which drive is which part of what mirror in the slightest. The space sacrificed is trivial compared to the convenience and safety net. I think I got both those suggestions on this list, and I would hope (assume?) that they have equivalents under ZFS. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services