From owner-freebsd-current@FreeBSD.ORG Tue Apr 1 06:42:56 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 7903B29C for ; Tue, 1 Apr 2014 06:42:56 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id AB2FD6AF for ; Tue, 1 Apr 2014 06:42:55 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA19208; Tue, 01 Apr 2014 09:42:41 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1WUsPB-000GkQ-EX; Tue, 01 Apr 2014 09:42:41 +0300 Message-ID: <533A5FA9.7030705@FreeBSD.org> Date: Tue, 01 Apr 2014 09:41:45 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "R. Tyler Croy" Subject: Re: ZFS panic in -CURRENT References: <20140328170021.7BE88D6@hub.freebsd.org> <20140331162232.45e300e7@monkeypox.org> In-Reply-To: <20140331162232.45e300e7@monkeypox.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org 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, 01 Apr 2014 06:42:56 -0000 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? > I'm running -CURRENT as of r263881 right now, with a custom kernel > which is built on top of the VT kernel > (https://github.com/rtyler/freebsd/blob/5e324960f1f2b7079de369204fe228db4a2ec99d/sys/amd64/conf/KIWI) > > I'm able to get this panic *consistently* whenever a process accesses > my maildir folder which I sync with the mbsync program (isync package), > such as `mbsync personal` or when I back up the maildir with duplicity. > The commonality seems to be listing or accessing portions of this file > tree. Curiously enough it only seems to be isolated to that single > portion of the filesystem tree. > > The zpool is also clean as far as errors go: > >> [16:11:03] tyler:freebsd git:(master*) $ zpool status zroot >> pool: zroot >> state: ONLINE >> status: Some supported features are not enabled on the pool. The pool >> can still be used, but some features are unavailable. >> action: Enable all features using 'zpool upgrade'. Once this is done, >> the pool may no longer be accessible by software that does not >> support the features. See zpool-features(7) for details. >> scan: scrub repaired 0 in 0h18m with 0 errors on Fri Mar 28 11:55:03 >> 2014 config: >> >> NAME STATE READ WRITE CKSUM >> zroot ONLINE 0 0 0 >> ada0p3.eli ONLINE 0 0 0 >> >> errors: No known data errors >> [16:19:57] tyler:freebsd git:(master*) $ > > > I'm not sure what other data would be useful here, I can consistently > see the panic, but this data is highly personal, so I'm not sure how > much of a "repro case" I can give folks. :( > > Cheers > -- Andriy Gapon