From owner-freebsd-fs@FreeBSD.ORG Thu Jan 3 17:10:15 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 1E68016A417 for ; Thu, 3 Jan 2008 17:10:15 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from ns.trinitel.com (186.161.36.72.static.reverse.ltdomains.com [72.36.161.186]) by mx1.freebsd.org (Postfix) with ESMTP id E720C13C447 for ; Thu, 3 Jan 2008 17:10:14 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from proton.storspeed.com (209-163-168-124.static.tenantsolutions.net [209.163.168.124] (may be forged)) (authenticated bits=0) by ns.trinitel.com (8.14.1/8.14.1) with ESMTP id m03HA7E6064403; Thu, 3 Jan 2008 11:10:07 -0600 (CST) (envelope-from anderson@freebsd.org) Message-ID: <477D16EE.6070804@freebsd.org> Date: Thu, 03 Jan 2008 11:10:06 -0600 From: Eric Anderson User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Peter Schuller References: <477B16BB.8070104@freebsd.org> <20080102070146.GH49874@cicely12.cicely.de> <477B8440.1020501@freebsd.org> <200801031750.31035.peter.schuller@infidyne.com> In-Reply-To: <200801031750.31035.peter.schuller@infidyne.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on ns.trinitel.com 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:10:15 -0000 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 :( Thanks, Eric