From owner-freebsd-current@FreeBSD.ORG Tue Apr 15 20:41:20 2014 Return-Path: Delivered-To: freebsd-current@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 ESMTPS id 4C3057F1 for ; Tue, 15 Apr 2014 20:41:20 +0000 (UTC) Received: from sanddollar.geekisp.com (sanddollar.geekisp.com [216.168.135.167]) by mx1.freebsd.org (Postfix) with SMTP id E9DB41A4B for ; Tue, 15 Apr 2014 20:41:19 +0000 (UTC) Received: (qmail 100 invoked by uid 1003); 15 Apr 2014 20:34:37 -0000 Received: from unknown (HELO ?10.10.2.81?) (tyler@monkeypox.org@64.125.69.200) by mail.geekisp.com with (DHE-RSA-AES128-SHA encrypted) SMTP; 15 Apr 2014 20:34:37 -0000 Message-ID: <534D97DA.80003@monkeypox.org> Date: Tue, 15 Apr 2014 13:34:34 -0700 From: "R. Tyler Croy" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: ZFS panic in -CURRENT References: <20140328170021.7BE88D6@hub.freebsd.org> <20140331162232.45e300e7@monkeypox.org> <533A5FA9.7030705@FreeBSD.org> <20140401065721.5317b538@monkeypox.org> In-Reply-To: <20140401065721.5317b538@monkeypox.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Apr 2014 20:41:20 -0000 (follow up below) On 04/01/2014 06:57, R. Tyler Croy wrote: > On Tue, 01 Apr 2014 09:41:45 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 02:22 R. Tyler Croy said the following: >>> Bumping this with more details >>> >>> On Fri, 28 Mar 2014 09:53:32 -0700 >>> R Tyler Croy wrote: >>> >>>> Apologies for the rough format here, I had to take a picture of >>>> this failure because I didn't know what else to do. >>>> >>>> >>>> >>>> I'm building off of the GitHub freebsd.git mirror here, and the >>>> latest commit in the tree is neel@'s "Add an ioctl to suspend.." >>>> >>>> My dmesg/pciconf are here: >>>> https://gist.github.com/rtyler/1faa854dff7c4396d9e8 >>> As linked before, the dmesg and `pciconf -lv` output can be found >>> here: >>> >>> Also in addition to the photo from before of the panic, here's >>> another reproduction photo: >>> >> Are you or have you even been running with any ZFS-related kernel >> patches? > Negative, I've never run any specific ZFS patches on this machine (or > any machine for that matter!) > > One other unique clue might be that I'm running with an encrypted > zpool, other than that, nothing fancy here. I've upgraded my machine to r264387 and I still experience the issue, here's the latest pretty picture of my panicked laptop :) The issue still seems to stem from a failed assertion in zap_leaf_lookup_closest() (http://svnweb.freebsd.org/base/head/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zap_leaf.c?revision=249195&view=markup#l446) but I'm not sure which assertion might be failing. This is somewhat problematic because I cannot perform *any* FS operations with the tainted directory tree, not even a `du -hcs *` to find out how much space I can never access again :P I can reproduce this consistently, if anybody has the time to get onto IRC (rtyler on Freenode and EFNet) and debug this, I can certainly act as remote hands with kdb to help ascertain more information about the panic. Cheers