From owner-freebsd-current@FreeBSD.ORG Wed Jul 22 18:41:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92D6F106564A for ; Wed, 22 Jul 2009 18:41:10 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yx0-f181.google.com (mail-yx0-f181.google.com [209.85.210.181]) by mx1.freebsd.org (Postfix) with ESMTP id 427CC8FC18 for ; Wed, 22 Jul 2009 18:41:10 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yxe11 with SMTP id 11so632780yxe.3 for ; Wed, 22 Jul 2009 11:41:09 -0700 (PDT) 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:content-type; bh=vjWnBgNqQrAIccYyPnBHXiPrIIK1MP0PYebU4tbXTp4=; b=xVZpojoumK/cBQEnXsIW9214cqGzh9BTOtxfQZVubdUC0izY4PmKaXRy9cymjZ44YR 75e5L7pNhAVLcwwNYYBTrswFzmV1p6g/bnfO+cy+ClZBkTWsLj+8zDZ/b8BOmAXrwFfC s8m+B0znSiCw9TFsbrkYOE3ZtoGXB0jbG8tqU= 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 :content-type; b=pf0IJWWHpJ0KnQWsMdXGh+33uGH5xz1Kc8s71uNb7ZRufqW54/FdnYXKr7bYiGRovE 2/96Xze9p/KgEk7SE0QturAZRMs0XhRSDr1qTU6oeNAAgltsIni4dxKaG3J0CYauQy0U 1z401SnEpRw/jtB/1ryRBjLhwUjtWhVyhBA3E= MIME-Version: 1.0 Received: by 10.150.146.12 with SMTP id t12mr1431675ybd.199.1248288069751; Wed, 22 Jul 2009 11:41:09 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 Jul 2009 11:41:09 -0700 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: ZFS pool corrupted on upgrade of -current (probably sata renaming) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2009 18:41:10 -0000 On Wed, Jul 22, 2009 at 6:12 AM, Nenhum_de_Nos wrote: > > On Wed, July 15, 2009 13:22, Freddie Cash wrote: > > On Tue, Jul 14, 2009 at 8:44 PM, Randy Bush wrote: > > > >> > # glabel label disk01 /dev/ad4 > >> > # glabel label disk02 /dev/ad6 > >> > # glabel label disk03 /dev/ad8 > >> > # zpool create pool raidz1 label/disk01 label/disk02 label/disk03 > >> > > >> > After that, you can shuffle the drives around in the system, and the > >> pool > >> > will continue to work correctly. > >> > >> ooooooo! i wish i had understood that when i built a large set of > >> mirrored raid. > >> > >> any way to hack it ex post facto? > >> > > > > Yep. It's as simple as: > > > > * label all the drives using glabel, while they're still attached to > the > > pool > > * use "zpool replace pool ad4 label/disk01" to replace 1 drive > > * wait for it to resilver > > * use "zpool replace pool ad6 label/disk02" to replace the next drive > > * repeat the resilver and replace until all the devices are replaced > > > > This is what I did to one of our servers. Works quite nicely. > > > > There's no need to detach anything. > > was all this supposed to work with raidz ? > > here it doesn't. > > harry# zpool status > pool: zdados > state: ONLINE > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > zdados ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > ad8 ONLINE 0 0 0 > ad10 ONLINE 0 0 0 > ad12 ONLINE 0 0 0 > > errors: No known data errors > harry# zpool detach zdados ad8 > cannot detach ad8: only applicable to mirror and replacing vdevs > Reread what you quoted. :) Note how there's no "detach" step. :) Just label and replace. -- Freddie Cash fjwcash@gmail.com