From owner-freebsd-fs@freebsd.org Wed Jan 11 04:47:34 2017 Return-Path: Delivered-To: freebsd-fs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13EF7CAA923 for ; Wed, 11 Jan 2017 04:47:34 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB624188B for ; Wed, 11 Jan 2017 04:47:33 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by mail-qk0-x231.google.com with SMTP id 11so98860611qkl.3 for ; Tue, 10 Jan 2017 20:47:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kraus-haus-org.20150623.gappssmtp.com; s=20150623; h=subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qhzIREb5w+x0MdYNcxyf9pproL/58Qu8+zog93ilClk=; b=2EtPmH/qRVzbEM+B+Mc/r+HqtNQaeiyeAZBSGdsY/cx4aXgRf4mettgye30fLFnJbv Jdl/kmdpyWfFnofFky1xD0RQR3RN2gv0OQCtNc5Ip3ajfg6Xbe4cwsLj4wrrgvePdpSw 3gnY50GfgGQES/0Sp6RAjWeGVxTJX8aqptJgIi6bQ+T/+lnBBInqnVXQgYF/oZ9g/5Gn nrIZRZ/nH0cJrOaM0dMHxm+EfCddgfjNIGZQ4T+XHuJe3kVeqWdk1b2DZgwmkZlf9jd/ MFplJMWz1bVODXOYnVGo0QvSvxobWRGq3S8F09J7lUCCrwrJaLXLC1xrW04E9xHIKX/h GBhg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:mime-version:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qhzIREb5w+x0MdYNcxyf9pproL/58Qu8+zog93ilClk=; b=QYvoPKKP26E2eMvCl0WknEkpEM1XqWzEqTzWWg5uCXoSnl5ld0osW+V1Rl/uMZfjZx 7u+EJDhL1s95yfnalGO+f073QVXTPepr9IIcp/HCeoOw3ItXATV2g1LF+5Z39ewZnt1Z BvC1TOmnFUgftJaPO0PJTZ9mWupoIKj30tcDU5kZv96c65uNu1il9slnoxAmFKupN9wI QOTgyU5HCD5ezJ1VW+FkNOsH5zL4YpGdJ2exPPFHhFbDkulHhKNQNrNqt6YvYD4Bd/s2 P6xwaKog+8eBqDlu15zbEehaVQMzLzVDVbJz93eu7HvS3kVNg+EkROqshIVzNxNRr66B V29w== X-Gm-Message-State: AIkVDXKZqpe50L3kJw9D6yNqZH4AS4L4w2xC+af+xoUsgVke//Hg709wDFTsGC1as8mNrg== X-Received: by 10.55.60.136 with SMTP id j130mr6103143qka.304.1484110052735; Tue, 10 Jan 2017 20:47:32 -0800 (PST) Received: from [192.168.2.65] (pool-74-109-188-83.albyny.fios.verizon.net. [74.109.188.83]) by smtp.gmail.com with ESMTPSA id h184sm3231587qkf.23.2017.01.10.20.47.32 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 10 Jan 2017 20:47:32 -0800 (PST) Subject: Re: Stupidly destroyed a ZFS pool by recreating with the same name Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Content-Type: text/plain; charset=us-ascii From: Paul Kraus In-Reply-To: <4d186184-c118-84db-4a53-d027eaa32d89@gmx.de> Date: Tue, 10 Jan 2017 23:47:35 -0500 Cc: freebsd-fs@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <2DA7964C-2481-4233-8BE4-6C0428A24B19@kraus-haus.org> References: <4d186184-c118-84db-4a53-d027eaa32d89@gmx.de> To: Christoph Pomaska X-Mailer: Apple Mail (2.3124) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jan 2017 04:47:34 -0000 > On Jan 7, 2017, at 7:12 AM, Christoph Pomaska = wrote: >=20 > I not-so-recently set up a ZFS data pool on my Arch Linux setup, = either for experimenting and also because I think that the concept is a = pretty cool thing. > Well, as you can read in the subject title, I recently accidentally = recreated the ZFS pool that died, because I switched some drives out, = instead of importing it (as not stupidly enough, I did it with the = option -f, that's why it didn't ask me anything though). What were all of the steps you went through ? Be as exact as possible. What was the configuration of the pool (mirror, raidz2, how many top = level vdevs) ? > So, is there ANY way to get the original pool or at least ANYTHING = back? If there was data redundancy AND you did not overwrite ALL the copies of = the data, then you should still be able to import the remaining good = parts of the pool, perhaps on a completely different system to keep it = from getting confused. And note that when you import you can change the name of the pool at = that time to avoid name space conflicts. Also note that you should never use -f (or kill -9) as the FIRST attempt = at anything. Please be patient as I am about to leave town for a week, so I amy not = respond back for a while. If the data was critical, put all the drives = involved that were not overwritten in a safe place until you have a good = idea how to get the data back.=