From owner-freebsd-stable@FreeBSD.ORG Sun Jul 25 20:50:02 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0E2B1065670 for ; Sun, 25 Jul 2010 20:50:02 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 83AA68FC20 for ; Sun, 25 Jul 2010 20:50:02 +0000 (UTC) Received: by fxm13 with SMTP id 13so6325806fxm.13 for ; Sun, 25 Jul 2010 13:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:newsgroups:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Yh48OEUY7mvBG+VPhjPslBtKfiR/syO7wkO5BxIbGvA=; b=NsPX3P/Doo0Mz+rsvsmsRddS180QUjdIel/FMu35mOoty7IBII3XksKaiwQa/eFmS5 zD25cCDEJqjuVDBZ/GlwPh1ndWp+vTe5hsQE+KEZ3YRR7sibjpZtgmndHcBat/OQhlmT XrUGsDokyg9wreD1q63zfCaSNIdhCm3mYvw08= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:newsgroups:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; b=RncqpQX9V+zwGmLLyySCmITg1cwZh5G8RzaqAXf9RIooXEsc91atqNmPirwdqVIX2E oqGZ6TXZot3YfpcrbH8lfZew9cT5aUie5yH2IoPg0Rp5XGQfruERThjuD+R1FJRCi0Kc xTKgnfFwEgonVWzs2xa/D2SLywaEQLCP8dDxM= Received: by 10.223.103.134 with SMTP id k6mr5571536fao.5.1280091001273; Sun, 25 Jul 2010 13:50:01 -0700 (PDT) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id e20sm1076950fak.23.2010.07.25.13.49.59 (version=SSLv3 cipher=RC4-MD5); Sun, 25 Jul 2010 13:50:00 -0700 (PDT) Message-ID: <4C4CA375.2030906@gmail.com> Date: Sun, 25 Jul 2010 23:49:57 +0300 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.9.1.11) Gecko/20100722 Thunderbird/3.0.6 MIME-Version: 1.0 Newsgroups: gmane.os.freebsd.stable To: Dan Langille References: <4C4C7B4A.7010003@langille.org> In-Reply-To: <4C4C7B4A.7010003@langille.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: zpool destroy causes panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jul 2010 20:50:02 -0000 25.07.2010 20:58, Dan Langille wrote: > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz2 ONLINE 0 0 0 > gpt/disk01 ONLINE 0 0 0 > gpt/disk02 ONLINE 0 0 0 > gpt/disk03 ONLINE 0 0 0 > gpt/disk04 ONLINE 0 0 0 > gpt/disk05 ONLINE 0 0 0 > /tmp/sparsefile1.img UNAVAIL 0 0 0 corrupted data > /tmp/sparsefile2.img UNAVAIL 0 0 0 corrupted data 0k, i'll try it from here. UNAVAIL means ZFS can't locate correct vdev for this pool member. Even if this file exists it's not used by ZFS because it lacks ZFS headers/footers. You can (I think so) reinsert empty file to the pool with: # zpool replace storage /tmp/sparsefile1.img /tmp/sparsefile1.img ^- pool ^- ZFS old vdev name ^- current file If you replace both files you can theoretically bring pool to fully consistent state. Also you can use md to convert files to devices: # mdconfig -a -t vnode -f /tmp/sparsefile1.img md0 And you can use md0 with your pool. -- Sphinx of black quartz judge my vow.