From owner-freebsd-fs@FreeBSD.ORG  Wed Nov 28 14:13:21 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
 by hub.freebsd.org (Postfix) with ESMTP id 9B4C9E1
 for <freebsd-fs@FreeBSD.org>; Wed, 28 Nov 2012 14:13:21 +0000 (UTC)
 (envelope-from avg@FreeBSD.org)
Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140])
 by mx1.freebsd.org (Postfix) with ESMTP id DDC428FC15
 for <freebsd-fs@FreeBSD.org>; Wed, 28 Nov 2012 14:13:20 +0000 (UTC)
Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua
 [212.40.38.101])
 by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA27127;
 Wed, 28 Nov 2012 16:13:17 +0200 (EET) (envelope-from avg@FreeBSD.org)
Message-ID: <50B61BFD.20509@FreeBSD.org>
Date: Wed, 28 Nov 2012 16:13:17 +0200
From: Andriy Gapon <avg@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Josh Beard <josh@signalboxes.net>
Subject: Re: ZFS: Panic when attempting to delete certain data
References: <CAHDrHStcfSJ-9ueSV+FujEsmAK3zMX2CAGVD6Xz_2gJAThu5Kg@mail.gmail.com>
 <50B50B04.8020109@FreeBSD.org>
 <CAHDrHSteXO2pzkUtG0WHcgChsyXiBk2of4P0gR7ccY5srWNdew@mail.gmail.com>
 <50B52CEC.9080208@FreeBSD.org>
 <CAHDrHSvsrwx5qEimdx7e6eHoXTLwQ1AeH80Nx8izA7BTfFb8Jg@mail.gmail.com>
 <50B5CFAF.8070306@FreeBSD.org>
 <CAHDrHSv8Tv6Yr9z0PzWFFOqZPLiTN9EkH6nQsEMr48sz+saizg@mail.gmail.com>
 <50B61672.2070406@FreeBSD.org>
 <CAHDrHSsVfeRSbSxe6W7qtHSfOi_DA6QXG38utKgQko7A49uoXQ@mail.gmail.com>
In-Reply-To: <CAHDrHSsVfeRSbSxe6W7qtHSfOi_DA6QXG38utKgQko7A49uoXQ@mail.gmail.com>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-fs@FreeBSD.org
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.14
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: Wed, 28 Nov 2012 14:13:21 -0000

on 28/11/2012 16:07 Josh Beard said the following:
> 
> 
> On Wed, Nov 28, 2012 at 6:49 AM, Andriy Gapon <avg@freebsd.org
> <mailto:avg@freebsd.org>> wrote:
>     This is something that I said earlier in the private conversation that I
>     mentioned:
> 
>     Andriy Gapon said:
>     > The relevant commits are r240632 and r240345.  I can't recall when I MFC-ed them
>     > to stable/9.  Most likely they are not in 9.1 releng branch.
>     [snip]
>     > I also don't have a good advice on how to fix the existing corruption.
>     > I'd probably go with using something like tar/cpio/pax to move data to fresh
>     > filesystem.  Please be sure to use latest stable/9 or 8 to not run into the
>     > issue again.
>     >
>     > zfs send/recv won't help, it would mindlessly replicate the corrupted
>     attributes.
> 
>     To this I might add that the bugs were not FreeBSD-specifc and they may be still
>     present in ZFS upstream and other ZFS ports.
> 
>     Thank you for the debugging information.
>     --
>     Andriy Gapon
> 
> 
> Andriy,
> 
> Does this mean re-creating the dataset (or the pool?) would resolve this under a
> recent stable/9 build would resolve this?
> 
> I have no problem doing so - as the data is redundant.
> 
> Thanks for your help on this.

As I've said above - it depends.
If you just do normal file operations then the problem should not re-appear.
If it does, then please report.

If you zfs send/recv data from older systems or other operating systems, then you
may run into the problem again.

-- 
Andriy Gapon