Date: Thu, 3 Jan 2008 11:18:25 -0600 From: Brooks Davis <brooks@freebsd.org> To: Eric Anderson <anderson@freebsd.org> Cc: freebsd-fs@freebsd.org, ticso@cicely.de Subject: Re: ZFS i/o errors - which disk is the problem? Message-ID: <20080103171825.GA28361@lor.one-eyed-alien.net> In-Reply-To: <477D16EE.6070804@freebsd.org> References: <477B16BB.8070104@freebsd.org> <20080102070146.GH49874@cicely12.cicely.de> <477B8440.1020501@freebsd.org> <200801031750.31035.peter.schuller@infidyne.com> <477D16EE.6070804@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] 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 >> disks that you are seeing checksum errors on are the ones seeing the >> faults. In your case both drives show checksum errors (for some reason). > > Yea, I suspect it's the cheesy SATA controller I stuck in the system. I > suppose I will rebuild my NFS server with different hardware :( We've definitely seen cases where hardware changes fixed ZFS checksum errors. In once case, a firmware upgrade on the raid controller fixed it. In another 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 ZFS was quite disturbing since we wouldn't have found them with UFS. -- Brooks [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHfRjgXY6L6fI4GtQRAuq3AJ936BpveFQhTBHDNJcED+abpsrtNQCg0d78 lVmsueyAeIh9dDHamgndOYU= =XUYN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080103171825.GA28361>