From owner-freebsd-fs@FreeBSD.ORG  Thu Nov 13 19:43:58 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 69010D18
 for <freebsd-fs@freebsd.org>; Thu, 13 Nov 2014 19:43:58 +0000 (UTC)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com
 [IPv6:2a00:1450:4010:c03::236])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id E0A29C25
 for <freebsd-fs@freebsd.org>; Thu, 13 Nov 2014 19:43:57 +0000 (UTC)
Received: by mail-la0-f54.google.com with SMTP id gf13so1946963lab.27
 for <freebsd-fs@freebsd.org>; Thu, 13 Nov 2014 11:43:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=ItoOwxe8aYFhNLfWVxNhMxP00KFRZN/gG9+IyaEML6M=;
 b=El7EysUX+hLJ2b5t13WmX0FMqY9eVRc6GpVmq2fxDWOcvKUB59cDwBhSXVQqV+m3nl
 CUAm2r7yXwwJlUcDZWpUDulwN4P8r0rz41d7S4rXrUiK8p/MUxmec3cdHoq/2/hMI1p9
 BHyDmuGF/YAiSETscbVHXr/R1Apos2wWHf+WWbAwgJNLKgpBP2Z26aX3aAK5+UW5zoMP
 VsjeKjX+cBUQeAEhTZMPVcEBA2KAAMKyVHUGdgBTtK3G2tKWuNItRoQqaHe+TwSrzmyf
 8wJLhfCNk9JPuC6I1j+By2xstVacCZ/EulMaOm1LEDbxlvb0zCQCWI89fIkjGReh7E0v
 L7PA==
MIME-Version: 1.0
X-Received: by 10.112.235.196 with SMTP id uo4mr4183026lbc.66.1415907835947;
 Thu, 13 Nov 2014 11:43:55 -0800 (PST)
Received: by 10.114.245.38 with HTTP; Thu, 13 Nov 2014 11:43:55 -0800 (PST)
Date: Thu, 13 Nov 2014 11:43:55 -0800
Message-ID: <CAP1HOmTNcSrJzw6H777iJvcKG+eCv5L+t0jcR7ccYX5eRXxhGg@mail.gmail.com>
Subject: ZFS + xattr -> panic loop
From: javocado <javocado@gmail.com>
To: FreeBSD Filesystems <freebsd-fs@freebsd.org>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Thu, 13 Nov 2014 19:43:58 -0000

After running an rsync (upload) into my zfs filesystem using the
--fake-super option (which stores permissions in extended attributes) the
zfs filesystem has somehow become corrupt. When booting the system it
panic's upon zfs startup:

panic: solaris assert: VFS_ROOT(vfsp, LK_EXCLUSIVE, &vp) == 0, file:
/usr/src/sys/modules/zfs/../../cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vfsops.c
, line: 1170
cpuid = 12
KDB: stack backtrace:
#0 0xffffffff8034b3ae at kdb_backtrace+0x5e
#1 0xffffffff803185c7 at panic+0x187
#2 0xffffffff80ab8213 at zfs_mount+0x563
#3 0xffffffff803a2635 at vfs_donmount+0xdc5
#4 0xffffffff803a3133 at nmount+0x63
#5 0xffffffff80553284 at amd64_syscall+0x1f4
#6 0xffffffff8053bc2c at Xfast_syscall+0xfc

I was able to boot the system by setting the filesystem:

canmount=off

However, I am still unable to mount it manually without causing a similar
panic.

So, setting the cause of the panic aside for the moment, I just want to get
to the data. I'd like to think I can do that by turning off xattrs and
mounting it read-only however:

# zfs set xattr=off pool/data
property 'xattr' not supported on FreeBSD: permission denied

How can I turn that off?

Second or alternately, if I want to just dump the filesystem out excluding
the extended attributes, so that I have a clean, mountable data set, how
would I do that?

Thank you!