From owner-freebsd-stable@FreeBSD.ORG  Mon Mar 24 06:06:34 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 56630B4A
 for <freebsd-stable@freebsd.org>; Mon, 24 Mar 2014 06:06:34 +0000 (UTC)
Received: from elf.hq.norma.perm.ru (mail.norma.perm.ru
 [IPv6:2001:470:1f09:14c0::2])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 02D45650
 for <freebsd-stable@freebsd.org>; Mon, 24 Mar 2014 06:06:33 +0000 (UTC)
Received: from bsdrookie.norma.com. (bsdrookie.norma.com [192.168.7.224])
 by elf.hq.norma.perm.ru (8.14.5/8.14.5) with ESMTP id s2O66TFe057121
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
 for <freebsd-stable@freebsd.org>; Mon, 24 Mar 2014 12:06:29 +0600 (YEKT)
 (envelope-from emz@norma.perm.ru)
Message-ID: <532FCB65.6060403@norma.perm.ru>
Date: Mon, 24 Mar 2014 12:06:29 +0600
From: "Eugene M. Zheganin" <emz@norma.perm.ru>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: freebsd-stable <freebsd-stable@freebsd.org>
Subject: Re: crash on zpool import - help get data back
References: <532BEABC.5050808@norma.perm.ru>	<532BF531.1050400@norma.perm.ru>	<532C0F76.8010605@norma.perm.ru>
 <CADbaceL=Gz7bmp6v4dChVPrJnCgLA0SDJyhw3YyQxM_h5dHVGQ@mail.gmail.com>
In-Reply-To: <CADbaceL=Gz7bmp6v4dChVPrJnCgLA0SDJyhw3YyQxM_h5dHVGQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7
 (elf.hq.norma.perm.ru [192.168.3.10]); Mon, 24 Mar 2014 12:06:30 +0600 (YEKT)
X-Spam-Status: No hits=-101.0 bayes=0.5 testhits ALL_TRUSTED=-1,
 USER_IN_WHITELIST=-100 autolearn=unavailable version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on elf.hq.norma.perm.ru
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Mar 2014 06:06:34 -0000

Hi.

On 24.03.2014 08:43, Christian Campbell wrote:
> I had a hosed FreeBSD ZFS pool once which I recovered with 'zpool
> import -f; zpool export' under an OpenIndiana live CD. 
>
I was able to read all of the data with rsync. I recreated the pool and
restored the data read. 'zfs send' was unable to read data - it was
crashing while reading 43th gig out of 1400, as well as the scrub was.
This whole thing is just sad - clearly something happened with the
labels, thus meaning that labels are somehow modified during normal zfs
work. Why ? For what reason ? How could the pool become corrupted on a
machine with non-corrupted memory ? So my advice to FreeBSD zfs users -
scrub periodically and be prepared for some doom to happen.

P.S. Saw a couple of minor issues with zfs on Solaris, but never such
terrible ones (and it can even swap onto zfs).

Eugene.