From owner-freebsd-fs@FreeBSD.ORG Wed Aug 14 19:56:06 2013 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E786426A for ; Wed, 14 Aug 2013 19:56:06 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A59AF22C9 for ; Wed, 14 Aug 2013 19:56:06 +0000 (UTC) Received: by mail-vb0-f53.google.com with SMTP id i3so7866121vbh.40 for ; Wed, 14 Aug 2013 12:56:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Agqwu/B50ArTrzztqnxO0/FZkHGZab4CTHEkCb/1vDo=; b=dDxd1cJvt786Yd3P785QOhXAL8cmgZgw/H81jlTobrqklOPBWVZvd9OAUjlnk4Ng3k de4uyfKBOWtrRlKiBRNwgLEcKlafSRYEVt66lDLxdjzsL5BQf8AiHtLAsu1uqFKoXObv glnG7mBqupnfGsbOZF8eJXNG68HVfEN0xVpCs6QKAERwrpUY+36fHQf5jALriMUWXKcI orDUX5WDvBUtiOUrnq+KZPeGJDZhm6Si/T11NHw/Yh+056ty4SN7N1ihGIl+ma41vETS qr3usK6Ietq9yMPNdgK5g+kiB21whcegbN8UWwPNLFATJqot4Vi1HcNeFmu4yk5lUwGH QZtQ== MIME-Version: 1.0 X-Received: by 10.52.34.74 with SMTP id x10mr9388554vdi.13.1376510165696; Wed, 14 Aug 2013 12:56:05 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.220.68.205 with HTTP; Wed, 14 Aug 2013 12:56:05 -0700 (PDT) In-Reply-To: <9274C3CA-36F5-4EDC-A645-C612C6D71E8A@melmac.net> References: <96CA3382-A3C7-472A-82C9-20C1ACACD5B9@melmac.net> <9274C3CA-36F5-4EDC-A645-C612C6D71E8A@melmac.net> Date: Wed, 14 Aug 2013 12:56:05 -0700 X-Google-Sender-Auth: lfzaXyMpRMIfcdkD5K9hdVcFwAQ Message-ID: Subject: Re: kernel panics because of the corrupted zpool meta-data From: Artem Belevich To: Stan Grishin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-fs X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Aug 2013 19:56:07 -0000 On Wed, Aug 14, 2013 at 12:44 PM, Stan Grishin wrote: > Artem, > > Thanks for you suggestion. No, I haven't tried that particular command. > But how can I get the transaction ID if even simple zpool import (no > parameters) causes kernel panics? > > "zdb -e" should work on un-imported pools. --Artem > -Stan > > On 2013-08-14, at 11:27 AM, Artem Belevich wrote: > > > > > On Wed, Aug 14, 2013 at 7:33 AM, Stan Grishin wrote: > >> As recommended in FreeBSD forums I'm posting the message here. >> >> I have a peculiar case where NAS4Free has corrupted the meta-data on my >> 4-disk raidz pool and a few flavours of FreeBSD and a latest version of >> OpenIndiana I've tried go down just when I try zpool import with no >> additional parameters (kernel panics). >> >> I have more or less given up of my precious data, but if any FreeBSD dev >> wants to investigate or help me fix the problem I'd gladly try any special >> build you'd want me to. >> >> PS. I've tried removing disks one by one, but any 3 out of 4 cause kernel >> panics and with just two I can't get my data back. >> >> PPS. zdb -l works and reports valid information about zpool >> configuration, but I can't fix any problems with zdb. >> >> > Did you try rolling back your pool to a previous state with 'zpool import > -T ' ? It will attempt to import the pool as it was at the time > particular transaction group was committed. > > Here's more info (it's for solaris, but should work on recent FreeBSD, > too): > http://www.c0t0d0s0.org/archives/7621-Back-in-time-or-zpool-import-T.html > > --Artem > > >