From owner-freebsd-current@FreeBSD.ORG  Tue Mar 11 15:00:01 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 E31ABA71;
 Tue, 11 Mar 2014 15:00:01 +0000 (UTC)
Received: from thyme.infocus-llc.com (server.infocus-llc.com [206.156.254.44])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B4661F5B;
 Tue, 11 Mar 2014 15:00:00 +0000 (UTC)
Received: from draco.over-yonder.net (c-75-65-60-66.hsd1.ms.comcast.net
 [75.65.60.66])
 (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by thyme.infocus-llc.com (Postfix) with ESMTPSA id 1950837B499;
 Tue, 11 Mar 2014 09:59:54 -0500 (CDT)
Received: by draco.over-yonder.net (Postfix, from userid 100)
 id 3fjzx54YJ3z1bn; Tue, 11 Mar 2014 09:59:53 -0500 (CDT)
Date: Tue, 11 Mar 2014 09:59:53 -0500
From: "Matthew D. Fuller" <fullermd@over-yonder.net>
To: Andriy Gapon <avg@FreeBSD.org>
Subject: Re: ZFS secondarycache on SSD problem on r255173
Message-ID: <20140311145953.GS32883@over-yonder.net>
References: <7059AA6DCC0D46B8B1D33FC883C31643@multiplay.co.uk>
 <20131017061248.GA15980@hell.ukr.net>
 <326B470C65A04BC4BC83E118185B935F@multiplay.co.uk>
 <20131017073925.GA34958@hell.ukr.net>
 <2AFE1CBD9B124E3AB9E05A4E483CCE03@multiplay.co.uk>
 <20131018080148.GA75226@hell.ukr.net>
 <256B2E5A0BA44DCBB45BB3F3E820E190@multiplay.co.uk>
 <20131018144524.GA30018@hell.ukr.net>
 <4459A6FAB7B8445C97CCB9EFF34FD4F0@multiplay.co.uk>
 <53144891.9050001@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53144891.9050001@FreeBSD.org>
X-Editor: vi
X-OS: FreeBSD <http://www.freebsd.org/>
User-Agent: Mutt/1.5.22 (2013-10-16)
X-Virus-Scanned: clamav-milter 0.98.1 at thyme.infocus-llc.com
X-Virus-Status: Clean
Cc: "Justin T. Gibbs" <gibbs@FreeBSD.org>, freebsd-current@FreeBSD.org,
 Steven Hartland <killing@multiplay.co.uk>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Mar 2014 15:00:02 -0000

On Mon, Mar 03, 2014 at 11:17:05AM +0200 I heard the voice of
Andriy Gapon, and lo! it spake thus:
> 
> I noticed that on some of our systems we were getting a clearly
> abnormal number of l2arc checksum errors accounted in l2_cksum_bad.
> The hardware appeared to be in good health.

FWIW, I have a system here where I see similar things; after
sufficient uptime it shows an impressive number and proportion of
checksum errors (50% or more of the hits, eventually), since at least
sometime last fall.  No indication anywhere else of problems (CAM,
SMART, zpool status).

Haven't tried the patches.  It would take most of a month of seeing
nothing to have much confidence they did anything anyway; it's got >2
weeks now and only ~500 errors, so it takes a long time with this
system/workload to ramp up.  But it'd be a nice fix to have, so mark
me up as a user-vote for landing if the code makes sense to the
codesense people.


-- 
Matthew Fuller     (MF4839)   |  fullermd@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
           On the Internet, nobody can hear you scream.