From owner-freebsd-fs@FreeBSD.ORG Fri Apr 1 10:34:45 2011 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 021B91065673 for ; Fri, 1 Apr 2011 10:34:45 +0000 (UTC) (envelope-from ppaczyn@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id B96918FC15 for ; Fri, 1 Apr 2011 10:34:44 +0000 (UTC) Received: by iyj12 with SMTP id 12so4248605iyj.13 for ; Fri, 01 Apr 2011 03:34:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4ElW7d7fg/pjX4VwvOfsuRxQ0ojVoVHTu9BB/oLwl8w=; b=UbT4tYA4MW202R+Dr7TpL/mv77cMx7+NkLH1d1+v/dhKY+p2hC6YTExBOEcOMEoMaZ 9AIKBzYeg3T3+t5fbQ36OtAklnfvaEC8eZmBLWUiyb+vjEuGgxZVpZrW8LW0nnzFkYqH 77yxA7rJjJVeT6n5F5ATrfSl1b/65HK2W+cdk= 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 :cc:content-type; b=sm+xuXlrvBLJvbf8ETtzHRw2/nShxmXmda9MuUKSsjysYYZwRaDA8jhE3nZ++RauIP bK8QL+NO8hiiINXWJQljp37kLigs07iufgLeHa5E5Vn4RaPW7U43oZj2htf07F0i3/eV hXprc53L2ECqndyoHpn7DEpTKhOij6/5yN7jk= MIME-Version: 1.0 Received: by 10.43.63.212 with SMTP id xf20mr1055427icb.265.1301654084071; Fri, 01 Apr 2011 03:34:44 -0700 (PDT) Received: by 10.42.172.201 with HTTP; Fri, 1 Apr 2011 03:34:44 -0700 (PDT) In-Reply-To: <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> References: <20110401013603.GA31034@icarus.home.lan> <84DF4838-CE43-430E-8C3A-4CC7881E44BD@gmail.com> Date: Fri, 1 Apr 2011 12:34:44 +0200 Message-ID: From: Piotr Paczynski To: =?UTF-8?Q?=C5=A0imun_Mikecin?= Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: ZFS failed after hard power off 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: Fri, 01 Apr 2011 10:34:45 -0000 >> I believe the command here is wrong, and that you should be using "zpool >> import 8416389847782759507" or "zpool import 8416389847782759507 zroot". >> I've seen many cases where using the pool name doesn't work. I can import the "backup" pool just fine using either its name or the guid. The zroot pool is the problem. > He has two pools: backup and zroot. Only backup is visible. > So he shouldn't do as you suggested, because it will rename his backup pool to zroot, which will bring the confusion, because it is not the original zroot pool. > To be able to import his original zroot pool, it needs to be visible to "zpool import" as a first step. Any idea how to make it visible to "zpool import"? I've tried importing the zroot pool using its various guids, as show by "zdb -l /dev/dsk/c3t0d0s2": version: 14 name: 'zroot' pool_guid: 2082617533358360017 top_guid: 1617266672942229358 but still no luck: root@openindiana:~# zpool import 2082617533358360017 cannot import '2082617533358360017': no such pool available root@openindiana:~# zpool import 1617266672942229358 cannot import '1617266672942229358': no such pool available