From owner-freebsd-fs@FreeBSD.ORG Fri Oct 24 15:00:56 2014 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C307CB09; Fri, 24 Oct 2014 15:00:56 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 80ED0E82; Fri, 24 Oct 2014 15:00:56 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id AEE4E64AE8; Fri, 24 Oct 2014 15:00:55 +0000 (UTC) Message-ID: <544A69B8.4020402@freebsd.org> Date: Fri, 24 Oct 2014 11:01:12 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Zaphod Beeblebrox , FreeBSD Hackers , freebsd-fs Subject: Re: ZFS errors on the array but not the disk. References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wkWRSt1dVbA0301swoKKkbEhTwaA6GPvs" 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: Fri, 24 Oct 2014 15:00:56 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wkWRSt1dVbA0301swoKKkbEhTwaA6GPvs Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-10-24 01:37, Zaphod Beeblebrox wrote: > What does it mean when checksum errors appear on the array (and the vde= v) > but not on any of the disks? See the paste below. One would think tha= t > there isn't some ephemeral data stored somewhere that is not one of the= > disks, yet "cksum" errors show only on the vdev and the array lines. H= elp? >=20 > [2:17:316]root@virtual:/vr2/torrent/in> zpool status > pool: vr2 > state: ONLINE > status: One or more devices is currently being resilvered. The pool wi= ll > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. > scan: resilver in progress since Thu Oct 23 23:11:29 2014 > 1.53T scanned out of 22.6T at 62.4M/s, 98h23m to go > 119G resilvered, 6.79% done > config: >=20 > NAME STATE READ WRITE CKSUM > vr2 ONLINE 0 0 36 > raidz1-0 ONLINE 0 0 72 > label/vr2-d0 ONLINE 0 0 0 > label/vr2-d1 ONLINE 0 0 0 > gpt/vr2-d2c ONLINE 0 0 0 block size: 512B= > configured, 4096B native (resilvering) > gpt/vr2-d3b ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-d4a ONLINE 0 0 0 block size: 512B= > configured, 4096B native > ada14 ONLINE 0 0 0 > label/vr2-d6 ONLINE 0 0 0 > label/vr2-d7c ONLINE 0 0 0 > label/vr2-d8 ONLINE 0 0 0 > raidz1-1 ONLINE 0 0 0 > gpt/vr2-e0 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e1 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e2 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e3 ONLINE 0 0 0 > gpt/vr2-e4 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e5 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e6 ONLINE 0 0 0 block size: 512B= > configured, 4096B native > gpt/vr2-e7 ONLINE 0 0 0 block size: 512B= > configured, 4096B native >=20 > errors: 43 data errors, use '-v' for a list > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 I am guessing they were on the disk that is now resilvering. I am not sure if resilvering causes the devices error count to get reset, but it would make sense if it is considered a 'replaced' disk. --=20 Allan Jude --wkWRSt1dVbA0301swoKKkbEhTwaA6GPvs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUSmm6AAoJEJrBFpNRJZKflAkP/Re9F3VJOXgQQSJbG8jV0fO/ n6EzHLVUezMJUndq26DX6zzsuXl/7uSAXoxMoY52i5M2nf3DmK1n0Nn1cx+/k9Mx 4vDKWSIhrZsWfoHPR8aJHjIUYd2SPdEcmmrXb5N21YVencPtzqfHjyvCWf71kx8A ZJsqQQ1CBAh0jfcPmGJXXLxbj/8I7LTW7JCAdsZX942SYx9D6qi45uD9mObw/DfJ QWFrFS/JrjBMHjnIUaSMmElpoHuXYekpdS7bpAE2B6jsXNh26aVmb2QEA/w4gmK9 2JE9Q/NBYx0E31m5kYfooQVXczvDo5fV/dNBqF8tNIOFtqLOi0b3I34mwH1uu+uy 28JMQf2OxW8PWkpGbe4X9D6CBqV0vZbM74zRsdkNneCUlbGL5ETbSNDbt3w4Z/Gc c6Mdx4uOulYGIqdp0Gb9/2SJgFrmQq/vNkzNPFkg3urzm/y6R/VlcqUbLDpG/JOH SKRoDcKyWSyAMBE7bN7Tdg6Atf2kNSJGTFkgLrJ4S+tLpjHFHg6vuJs2NEDlVZ+0 3p5RvsjKfz+H/3WLyrIaqPXVYS1PCugMCGTDC3TCdtbMBHzl6yrCmj2vJYsM4H0c Cdvfy0wUTFnAXxb7BLFakrIMybhxEHhfgFVx60jN4jmWAmFtd6FYf5cdL4KkG2AL msJ7+3WYt7ZvRCPi10ip =2rG4 -----END PGP SIGNATURE----- --wkWRSt1dVbA0301swoKKkbEhTwaA6GPvs--