From owner-freebsd-stable@FreeBSD.ORG Sun Jul 25 20:41:09 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 DBE8F1065673 for ; Sun, 25 Jul 2010 20:41:09 +0000 (UTC) (envelope-from dan@langille.org) Received: from nyi.unixathome.org (nyi.unixathome.org [64.147.113.42]) by mx1.freebsd.org (Postfix) with ESMTP id C55F88FC0A for ; Sun, 25 Jul 2010 20:41:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by nyi.unixathome.org (Postfix) with ESMTP id 2EAA850B7B; Sun, 25 Jul 2010 21:41:09 +0100 (BST) X-Virus-Scanned: amavisd-new at unixathome.org Received: from nyi.unixathome.org ([127.0.0.1]) by localhost (nyi.unixathome.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UR517lGBnTHT; Sun, 25 Jul 2010 21:41:07 +0100 (BST) Received: from smtp-auth.unixathome.org (smtp-auth.unixathome.org [10.4.7.7]) (Authenticated sender: hidden) by nyi.unixathome.org (Postfix) with ESMTPSA id D490850B1B ; Sun, 25 Jul 2010 21:41:05 +0100 (BST) Message-ID: <4C4CA157.9000103@langille.org> Date: Sun, 25 Jul 2010 16:40:55 -0400 From: Dan Langille Organization: The FreeBSD Diary User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 MIME-Version: 1.0 To: Volodymyr Kostyrko References: <4C4C7B4A.7010003@langille.org> <20100725201811.GA33611@icarus.home.lan> <4C4CA091.1090406@gmail.com> In-Reply-To: <4C4CA091.1090406@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Jeremy Chadwick 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:41:09 -0000 On 7/25/2010 4:37 PM, Volodymyr Kostyrko wrote: > 25.07.2010 23:18, Jeremy Chadwick wrote: >> Footnote: can someone explain to me how ZFS would, upon reboot, know >> that /tmp/sparsefile[12].img are part of the pool? How would ZFS taste >> metadata in this situation? > > Just hacking it. > > Each ZFS device which is part of the pool tracks all other devices which > are part of the pool with their sizes, device ids, last known points. It > doesn't know that /tmp/sparsefile[12].img is part of the pool, yet it > does know that pool have had some /tmp/sparsefile[12].img before and now > they can't be found or current contents doesn't look like ZFS device. > > Can you try moving current files to /tmp/sparsefile[34].img and then > readd them to the pool with zpool replace? One by one please. I do not know what the above paragraph means. -- Dan Langille - http://langille.org/