From owner-freebsd-fs@freebsd.org  Fri Jul 10 16:35:57 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
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 4EA8A997B41
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 10 Jul 2015 16:35:57 +0000 (UTC)
 (envelope-from arcade@b1t.name)
Received: from limbo.b1t.name (limbo.b1t.name [213.111.203.167])
 by mx1.freebsd.org (Postfix) with ESMTP id EBEDC16EF
 for <freebsd-fs@freebsd.org>; Fri, 10 Jul 2015 16:35:56 +0000 (UTC)
 (envelope-from arcade@b1t.name)
Received: from limbo.b1t.name (limbo.b1t.name [213.111.203.167])
 by limbo.b1t.name (Postfix) with ESMTPSA id A812A6C
 for <freebsd-fs@freebsd.org>; Fri, 10 Jul 2015 19:35:44 +0300 (EEST)
Message-ID: <559FF45E.1090100@b1t.name>
Date: Fri, 10 Jul 2015 19:35:42 +0300
From: Volodymyr Kostyrko <arcade@b1t.name>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: freebsd-fs@freebsd.org
Subject: Re: Crashed ZFS pool
References: <559CEDC3.2040107@harmless.hu>
In-Reply-To: <559CEDC3.2040107@harmless.hu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Jul 2015 16:35:57 -0000

On 08.07.2015 12:30, Gergely Czuczy wrote:

> So, anyone has any idea what to do with it? It would be nice to get it
> back to a functional state. Or at least to a state where the data can be
> accessed.

Have you tried to import pool with:

1. Read-only mode. ( -o readonly=on )
2. Unmounted. ( -N )
3. Checking whether some previous transactions are good. ( -Fn and then -F).

There are also extra options made for debugging:

1. -X - xtreem rewind, tries transactions scrubbing each next one.
2. -T txg - specify a starting txg for import. Might be particulary 
useful if some previous transactions are not only damaged beyond repair 
but also make system dump core.

Once in my life I had a problem with a pool that I ought to use -T - the 
controller was buggy and last few transactions were damaged badly.

-- 
Sphinx of black quartz judge my vow.