From owner-freebsd-current@FreeBSD.ORG Wed Apr 2 19:07:33 2014 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C582C62 for ; Wed, 2 Apr 2014 19:07:33 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BB096D06 for ; Wed, 2 Apr 2014 19:07:32 +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 WAA18502; Wed, 02 Apr 2014 22:07:28 +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 1WVQVU-000Lor-0Y; Wed, 02 Apr 2014 22:07:28 +0300 Message-ID: <533C5FB7.2040703@FreeBSD.org> Date: Wed, 02 Apr 2014 22:06:31 +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> <533A5FA9.7030705@FreeBSD.org> <20140401065721.5317b538@monkeypox.org> <533BB51D.2040100@FreeBSD.org> <20140402094854.572247b5@monkeypox.org> In-Reply-To: <20140402094854.572247b5@monkeypox.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 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: Wed, 02 Apr 2014 19:07:33 -0000 on 02/04/2014 19:48 R. Tyler Croy said the following: > On Wed, 02 Apr 2014 09:58:37 +0300 > Andriy Gapon wrote: > >> on 01/04/2014 16:57 R. Tyler Croy said the following: >>> On Tue, 01 Apr 2014 09:41:45 +0300 >>> Andriy Gapon 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: >>>>> >>>> >>>> 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? I am afraid that this is a different kind of corruption. Either a bug (possibly old, already fixes) in ZFS or a corruption that happened in RAM before a buffer was sent to a disk. -- Andriy Gapon