From owner-freebsd-fs@FreeBSD.ORG Wed Oct 24 15:35:36 2007 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CEDE016A417 for ; Wed, 24 Oct 2007 15:35:36 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 98D5F13C494 for ; Wed, 24 Oct 2007 15:35:36 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 29F8884423 for ; Wed, 24 Oct 2007 17:35:23 +0200 (CEST) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 74543-09 for ; Wed, 24 Oct 2007 17:35:15 +0200 (CEST) Received: from japan.t-online.private (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id 4CB5284420 for ; Wed, 24 Oct 2007 17:35:15 +0200 (CEST) Message-ID: <471F6632.5070506@fsn.hu> Date: Wed, 24 Oct 2007 17:35:14 +0200 From: Attila Nagy User-Agent: Thunderbird 2.0.0.0 (X11/20070421) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <471F5B46.9050106@fsn.hu> In-Reply-To: <471F5B46.9050106@fsn.hu> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: Re: ZFS and disk naming change (ex. da0->da4) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2007 15:35:36 -0000 On 10/24/07 16:48, Attila Nagy wrote: > Hello, > > I have an experimental (but that does not mean, I wouldn't like to get > my data back :) zpool, which was created with something like this: > zpool create people raidz2 /dev/da0 /dev/da3 /dev/da4, etc > > The problem is those device names have been changed during the next > reboot (the cause of this is irrelevant, but mainly because some of > them were not attached at the original boot, just later, so at the > next reboot the disks came up in a different order), so now I have: > zpool status > pool: people > state: UNAVAIL > status: One or more devices could not be opened. There are insufficient > replicas for the pool to continue functioning. > action: Attach the missing device and online it using 'zpool online'. > see: http://www.sun.com/msg/ZFS-8000-D3 > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > people UNAVAIL 0 0 0 insufficient replicas > raidz2 UNAVAIL 0 0 0 insufficient replicas > da0 UNAVAIL 0 0 0 cannot open > da3 ONLINE 0 0 0 > da4 FAULTED 0 0 0 corrupted data > da5 FAULTED 0 0 0 corrupted data > da6 FAULTED 0 0 0 corrupted data > da7 FAULTED 0 0 0 corrupted data > da8 FAULTED 0 0 0 corrupted data > da9 FAULTED 0 0 0 corrupted data > > (it seems da3 is still da3 :) > > My question is: what now? Is it possible to regain the pool, or is it > totally busted now? I am not sure that I can figure out which device > is which now... > > I've only played with ZFS on Solaris with FC targets, and there I've > never faced this problem, because of the static naming. > > ps: I guess next time I will use glabel -I love that- to provide base > devices... > > Thanks, > I reply to myself: rm /boot/zfs/zpool.cache reboot (I don't know the internals, maybe it can be solved without that) zfs import people -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/