From owner-freebsd-fs@FreeBSD.ORG Fri Jun 10 09:33:20 2011 Return-Path: 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 B1E83106566B for ; Fri, 10 Jun 2011 09:33:20 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by mx1.freebsd.org (Postfix) with ESMTP id 9AC518FC08 for ; Fri, 10 Jun 2011 09:33:20 +0000 (UTC) Received: from omta21.emeryville.ca.mail.comcast.net ([76.96.30.88]) by qmta13.emeryville.ca.mail.comcast.net with comcast id u9Wd1g0031u4NiLAD9ZJhh; Fri, 10 Jun 2011 09:33:18 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta21.emeryville.ca.mail.comcast.net with comcast id u9Z11g00F1t3BNj8h9Z1jp; Fri, 10 Jun 2011 09:33:02 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id E77DC102C19; Fri, 10 Jun 2011 02:33:18 -0700 (PDT) Date: Fri, 10 Jun 2011 02:33:18 -0700 From: Jeremy Chadwick To: Karl Pielorz Message-ID: <20110610093318.GA39276@icarus.home.lan> References: <729A0755FAEF480774EEF4AB@HexaDeca64.dmpriest.net.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <729A0755FAEF480774EEF4AB@HexaDeca64.dmpriest.net.uk> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-fs@freebsd.org Subject: Re: ZFS scrub 'repaired' pool with no chksum or read errors? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jun 2011 09:33:20 -0000 On Fri, Jun 10, 2011 at 09:43:14AM +0100, Karl Pielorz wrote: > I'm running FreeBSD-8.2R amd64 w/4Gb of ECC RAM on a machine used > for 'offsite' backups (that are copied to it using zfs > send/receive). > > I scrub this machine every now and again (about once a month) - > recently this resulted in the following output after the scrub > completed: > > " > # zpool status > pool: vol > state: ONLINE > scrub: scrub completed after 2h49m with 0 errors on Thu Jun 9 > 17:09:31 2011 > config: > > NAME STATE READ WRITE CKSUM > vol ONLINE 0 0 0 > raidz1 ONLINE 0 0 0 > ada0 ONLINE 0 0 0 256K repaired > ada1 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > > errors: No known data errors > " > > Should I be worried there was 256k of 'repairs' done, even though > there were no checksum errors, or read errors detected? > > The console logged no errors - and nothing shows in syslog. > > The machine is always cleanly shut down - and the drives all appear > fine from a SMART point of view - I'm just a bit concerned as to > where the repairs came from - as ZFS doesn't seem to know (or be > able to tell me) either :) ZFS experts please correct me, but my experience with this has shown me that the scrub itself found actual issues while analysing all data on the entire pool -- more specifically, I believe READ/WRITE/CKSUM are counters used for when errors are encountered during normal (read: non-scrub) operations. It's been a while since I've seen this happen, but have seen it on our Solaris 10 machines at my workplace. I've never been sure what it means; possibly signs of "bit rot"? If you're worried about your disk (ada0), please provide output from "smartctl -a /dev/ada0" and I'll be more than happy to review the output and provide you with any insights. I do believe you when you say it looks fine, but every model of disk is different in some regard. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |