From owner-freebsd-current@FreeBSD.ORG Tue Jul 14 22:50:49 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 53B8B1065773 for ; Tue, 14 Jul 2009 22:50:49 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-gx0-f217.google.com (mail-gx0-f217.google.com [209.85.217.217]) by mx1.freebsd.org (Postfix) with ESMTP id 057F88FC0C for ; Tue, 14 Jul 2009 22:50:48 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by gxk17 with SMTP id 17so4670261gxk.19 for ; Tue, 14 Jul 2009 15:50:48 -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=O1fBwNab5ShBXOz/m/DZ9PV9VFdtOigU1aNpLSaCRtk=; b=YbVK9gdMdbKmb3H++qZ7530aiN7U3Xp4TutWpcL6pQz5iZ9N7eLldEV7kS6DWhtdkv RViw98q/4TWTlscazrnWXW2kQER7D8/d/0Op6l9rh7ACb4IU1/wnD4XBHx9j0rM3HY2c E2xYX29Otn/+AhLZmqTd1WCEOKzUggB93kaOU= 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=lKH1Aper4b4KHT8nrrsbEjjXUKaWSDbjYJSF7yD7/ut+X8J1wioQbe2RKQt0S31WGU kPdXTpaB1cK4Kvm2VF5zkuDiPc56eU3UMDspQGZSmoBmH88K7l9eG7mU2tpLPkBDtG77 aRB3TdcUKWwLWrYdbLwK/L4Wqy/retLieip70= MIME-Version: 1.0 Received: by 10.150.197.21 with SMTP id u21mr11181657ybf.311.1247611847945; Tue, 14 Jul 2009 15:50:47 -0700 (PDT) In-Reply-To: References: Date: Tue, 14 Jul 2009 15:50:47 -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: Tue, 14 Jul 2009 22:50:49 -0000 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. -- Freddie Cash fjwcash@gmail.com