From owner-freebsd-fs@FreeBSD.ORG  Thu Jun 21 22:01:31 2012
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 2235E106566C
	for <freebsd-fs@freebsd.org>; Thu, 21 Jun 2012 22:01:31 +0000 (UTC)
	(envelope-from feld@feld.me)
Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2])
	by mx1.freebsd.org (Postfix) with ESMTP id E917F8FC0A
	for <freebsd-fs@freebsd.org>; Thu, 21 Jun 2012 22:01:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me;
	s=blargle; 
	h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type;
	bh=I2MTCUO7HmyCep8oJWzFZOgZz1k9A4OvcN4I/2rOg2I=; 
	b=iGlyDP1hUPzxek8jMktpKrzGbh6pbqFoc2Ulg4ax7wIRma1qCD1zxJxT+87twtMkdcHl43mub8zBPBOxJJwqisymNhMt7vmHHtTFQYJwsFm3/6qfMPjuMgVBS4Y7FTwH;
Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org)
	by feld.me with esmtp (Exim 4.77 (FreeBSD))
	(envelope-from <feld@feld.me>) id 1ShpRS-000MVT-8i
	for freebsd-fs@freebsd.org; Thu, 21 Jun 2012 17:01:30 -0500
Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4)
	with esmtpa id 1340316089-94480-94479/5/36; Thu, 21 Jun 2012 22:01:29
	+0000
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: freebsd-fs@freebsd.org
References: <E22D2EF22A824CC3A0386E62F407F262@multiplay.co.uk>
	<566221263.21373.1340225701396.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net>
	<CAGMYy3tW3By4RLj1=q_-NN7GYS_Yv2QY64A4p0z1x8VDe5F-Hg@mail.gmail.com>
	<1953965235.30115.1340315339964.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net>
Date: Thu, 21 Jun 2012 17:01:29 -0500
Mime-Version: 1.0
From: Mark Felder <feld@feld.me>
Message-Id: <op.wf9wsrl234t2sn@tech304>
In-Reply-To: <1953965235.30115.1340315339964.JavaMail.root@sz0192a.westchester.pa.mail.comcast.net>
User-Agent: Opera Mail/12.00 (FreeBSD)
X-SA-Score: -1.5
Subject: Re: ZFS Checksum errors
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
	<mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Jun 2012 22:01:31 -0000

On Thu, 21 Jun 2012 16:48:59 -0500, <rondzierwa@comcast.net> wrote:

> this is causing a lot of down time, and its making linux look very  
> attractive in my organization. how do I get this untangled short of  
> reformatting and starting over?

I'm pretty confident that you have bad hardware and ZFS is telling you so.  
It's either a memory issue (ECC RAM being used?), or a problem with your  
controller, cabling, or HDD. Things like this have happened to people and  
the problem was a faulty power supply or dirty power, too.

When ZFS tells you there are errors and checksum mismatches it's doing its  
best to PROTECT you from corrupted data and you need to start looking at  
every piece of hardware in your server that can cause this.