From owner-freebsd-fs@FreeBSD.ORG Thu Jan 3 17:18:31 2008 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 9602516A417; Thu, 3 Jan 2008 17:18:31 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (cl-162.ewr-01.us.sixxs.net [IPv6:2001:4830:1200:a1::2]) by mx1.freebsd.org (Postfix) with ESMTP id A22C813C467; Thu, 3 Jan 2008 17:18:30 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.1/8.13.8) with ESMTP id m03HIPrl029818; Thu, 3 Jan 2008 11:18:25 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.1/8.13.8/Submit) id m03HIP8E029817; Thu, 3 Jan 2008 11:18:25 -0600 (CST) (envelope-from brooks) Date: Thu, 3 Jan 2008 11:18:25 -0600 From: Brooks Davis To: Eric Anderson Message-ID: <20080103171825.GA28361@lor.one-eyed-alien.net> References: <477B16BB.8070104@freebsd.org> <20080102070146.GH49874@cicely12.cicely.de> <477B8440.1020501@freebsd.org> <200801031750.31035.peter.schuller@infidyne.com> <477D16EE.6070804@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: <477D16EE.6070804@freebsd.org> User-Agent: Mutt/1.5.16 (2007-06-09) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Thu, 03 Jan 2008 11:18:25 -0600 (CST) Cc: freebsd-fs@freebsd.org, ticso@cicely.de Subject: Re: ZFS i/o errors - which disk is the problem? 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: Thu, 03 Jan 2008 17:18:31 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 03, 2008 at 11:10:06AM -0600, Eric Anderson wrote: > Peter Schuller wrote: >>> I can believe a problematic SATA controller (it's an add-on PCI board), >>> but does anyone know of a way to ask ZFS which devices in a pool it >>> thinks has issues? >> That is exactly what zpool status is intended to tell you. That is, the= =20 >> disks that you are seeing checksum errors on are the ones seeing the=20 >> faults. In your case both drives show checksum errors (for some reason). >=20 > Yea, I suspect it's the cheesy SATA controller I stuck in the system. I= =20 > suppose I will rebuild my NFS server with different hardware :( We've definitely seen cases where hardware changes fixed ZFS checksum error= s. In once case, a firmware upgrade on the raid controller fixed it. In anoth= er case, we'd been connecting to an external array with a SCSI card that didn't have a PCI bracket and the errors went away when the replacement one arrived and was installed. The fact that there were significant errors caught by Z= FS was quite disturbing since we wouldn't have found them with UFS. -- Brooks --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHfRjgXY6L6fI4GtQRAuq3AJ936BpveFQhTBHDNJcED+abpsrtNQCg0d78 lVmsueyAeIh9dDHamgndOYU= =XUYN -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--