Date: Wed, 2 Apr 2014 09:48:54 -0700 From: "R. Tyler Croy" <tyler@monkeypox.org> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: ZFS panic in -CURRENT Message-ID: <20140402094854.572247b5@monkeypox.org> In-Reply-To: <533BB51D.2040100@FreeBSD.org> References: <20140328170021.7BE88D6@hub.freebsd.org> <20140331162232.45e300e7@monkeypox.org> <533A5FA9.7030705@FreeBSD.org> <20140401065721.5317b538@monkeypox.org> <533BB51D.2040100@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 02 Apr 2014 09:58:37 +0300 Andriy Gapon <avg@FreeBSD.org> wrote: > on 01/04/2014 16:57 R. Tyler Croy said the following: > > On Tue, 01 Apr 2014 09:41:45 +0300 > > Andriy Gapon <avg@FreeBSD.org> wrote: > > > >> on 01/04/2014 02:22 R. Tyler Croy said the following: > ... > >>> 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? > > > > > > 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. > > Your problem looks like a corruption of on-disk data. > I can not say how it came to be or how to fix it now. > This is concerning to me, I'm using an intel 128GB SSD which is less than 6 months old. If there is an actual disk-level corruption, shouldn't that manifest itself as a zpool error? :/ -- - R. Tyler Croy ------------------------------------------------------ Code: <https://github.com/rtyler>; Chatter: <https://twitter.com/agentdero>; % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F ------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140402094854.572247b5>