From owner-freebsd-current@FreeBSD.ORG Tue Jul 14 22:58:03 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 463C41065677 for ; Tue, 14 Jul 2009 22:58:03 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from atmail-6.bnguk.net (atmail-6.bnguk.net [80.74.253.20]) by mx1.freebsd.org (Postfix) with ESMTP id F33AF8FC16 for ; Tue, 14 Jul 2009 22:58:02 +0000 (UTC) (envelope-from freebsd-current@chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com) by atmail-6.bnguk.net with esmtp (Exim 4.69) (envelope-from ) id 1MQqwj-0001bx-NF for freebsd-current@freebsd.org; Tue, 14 Jul 2009 23:58:02 +0100 Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id AB6DDC10587; Tue, 14 Jul 2009 23:57:59 +0100 (BST) X-Virus-Scanned: amavisd-new at chrishedley.com Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9gBKGyb0Ze9d; Tue, 14 Jul 2009 23:57:54 +0100 (BST) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 3021EC10586; Tue, 14 Jul 2009 23:57:54 +0100 (BST) Date: Tue, 14 Jul 2009 23:57:54 +0100 (BST) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: Freddie Cash In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org 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: Tue, 14 Jul 2009 22:58:03 -0000 On Tue, 14 Jul 2009, Freddie Cash wrote: > While I don't have any insight into how to repair this issue you've run into > (at least not off-hand), one way to mitigate/prevent this from happening is > to use glabel to label the drives, and then use the labels to create the > zpool. That way, it doesn't matter where the physical devices are located > in the system, nor what the physical device nodes are called, as zpool just > looks for the label, and GEOM handles all the heavy lifting/translating for > you. > > # 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. Thanks - that was just what I was looking for! That'll save me an awful lot of hassle in future, especially as I'm eyeing up the CAM integration patch. In the meantime I'm successfully but slowly retrieving my data, I'll just have to be patient, but it's reassuring that I can build a new ZFS array with confidence. Cheers, Chris.