From owner-freebsd-stable@FreeBSD.ORG Sun Jul 25 21:06:14 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 3A144106567C for ; Sun, 25 Jul 2010 21:06:14 +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 C94508FC2A for ; Sun, 25 Jul 2010 21:06:13 +0000 (UTC) Received: by fxm13 with SMTP id 13so6329106fxm.13 for ; Sun, 25 Jul 2010 14:06:12 -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=Sb3NAC8AVH+JbclQCn5VGFQLY55lsnz63jUx2KenAO4=; b=oOI0wb/winnfbPIznhtTwbAXHakirwK1NmlDl+Uq4CuWSYs32h5azFTuR/O+cc/uhl Uo2j/wP1eJ6x9BTJIswS8pA2ueef+76Bcvjdcg2nDjwEEixD8c8PqtfCZEU3BuDuav1G r3+ZKnZ6W4q7CDpC90ZTE8lQipb+2qB/nlUPk= 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=APPZ8TzYnialkQRG4TW6Z35SGIrn21IQZ3rX4yHM0/OJuvI5sJtmpp5upXfCdU3/Ee rWij8SDnWtHYdf1xWxudi8oluPuJSXAM/PruteBDFmwczPWcJetGRrtS8Jxk0mqm7cRR NsE2Q99vxEfl/fo0vFE8qd+N0JHt5sVGgSrKo= Received: by 10.86.71.4 with SMTP id t4mr4230432fga.5.1280090263375; Sun, 25 Jul 2010 13:37:43 -0700 (PDT) Received: from limbo.lan ([193.33.173.33]) by mx.google.com with ESMTPS id c5sm1071758fac.43.2010.07.25.13.37.41 (version=SSLv3 cipher=RC4-MD5); Sun, 25 Jul 2010 13:37:41 -0700 (PDT) Message-ID: <4C4CA091.1090406@gmail.com> Date: Sun, 25 Jul 2010 23:37:37 +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: Jeremy Chadwick References: <4C4C7B4A.7010003@langille.org> <20100725201811.GA33611@icarus.home.lan> In-Reply-To: <20100725201811.GA33611@icarus.home.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, Dan Langille 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 21:06:14 -0000 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. -- Sphinx of black quartz judge my vow.