From owner-freebsd-fs@FreeBSD.ORG Sun Jan 18 03:15:22 2015 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA60C7DA for ; Sun, 18 Jan 2015 03:15:22 +0000 (UTC) Received: from zulu.iotz.org (zulu.iotz.org [192.73.233.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 831BCF3E for ; Sun, 18 Jan 2015 03:15:21 +0000 (UTC) Received: from iozz.us (zulu.iotz.org [192.73.233.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by zulu.iotz.org (Postfix) with ESMTPSA id 038271E0117; Sat, 17 Jan 2015 22:07:42 -0500 (EST) Date: Sat, 17 Jan 2015 22:07:31 -0500 From: Brian N To: Sean Chittenden Subject: Re: ZFS scrub on new disks gives cksum errors Message-ID: <20150118030731.GA6247@iozz.us> References: <20141208155230.GA574@iozz.us> <5485CB35.5010608@multiplay.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-fs@freebsd.org X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2015 03:15:22 -0000 On Mon, Dec 08, 2014 at 09:09:51AM -0800, Sean Chittenden wrote: > I had this exact problem at home on my FreeNAS host when a box is plugged > in to residential power that is "not clean." If you plug this host in to a > UPS it should clear things up instantly (find a sine wave UPS, not a > digital stepping supply). There's something about the fluctuating power or > brownouts that ZFS is well suited to detecting (and became terrifying to me > because wtf happened in the past pre-ZFS??). FWIW, I've tested the two drives attached to another PC with UPS clean power and have not seen the aforementioned errors. Not a scientific finding but moving to a UPS power source may have fixed my issue. Thanks.