Date: Tue, 01 Apr 2014 09:41:45 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: "R. Tyler Croy" <tyler@monkeypox.org> Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS panic in -CURRENT Message-ID: <533A5FA9.7030705@FreeBSD.org> In-Reply-To: <20140331162232.45e300e7@monkeypox.org> References: <20140328170021.7BE88D6@hub.freebsd.org> <20140331162232.45e300e7@monkeypox.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <tyler@monkeypox.org> 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. >> >> <http://www.flickr.com/photos/agentdero/13469355463/>; >> >> 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: > <https://gist.github.com/rtyler/1faa854dff7c4396d9e8>; > > Also in addition to the photo from before of the panic, here's another > reproduction photo: > <https://www.flickr.com/photos/agentdero/13472248423/>; 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?533A5FA9.7030705>