From owner-freebsd-fs@FreeBSD.ORG Sun Jan 24 05:28:57 2010 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 42ED7106566B for ; Sun, 24 Jan 2010 05:28:57 +0000 (UTC) (envelope-from rincebrain@gmail.com) Received: from mail-fx0-f226.google.com (mail-fx0-f226.google.com [209.85.220.226]) by mx1.freebsd.org (Postfix) with ESMTP id C5D908FC08 for ; Sun, 24 Jan 2010 05:28:56 +0000 (UTC) Received: by fxm26 with SMTP id 26so98315fxm.13 for ; Sat, 23 Jan 2010 21:28:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=iBNFAIOksWlGJXAx95WMi+PXf3AKiPhvnv9+QALUzZA=; b=YAFL8iF+luxjTEeskvKlrtX3t1Ue3YtbwFPiD1QvArIozCxGkmuj28C8YY5lgBEYnS wR4AV1HAtG2eV36QftlhrQJ41CUBLg/y79M1t78q0djKBxxIP3kBo4FmlJ/PBJbGIPPx iPfETqhAAy05bVI67qCzBA0L21o5hTgJblgeg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=A8FL3f0lS2W3byKv3nETl+k2qNL46fwadepBZyOzfuBSp8mp9akOLSGO9+ZmAXg2vk xsSno6Y4z5vwo/5179QYhcoOnBT6FKIJc9L50ETX+QWCm1cZ2lHUPoTMR9jc3IbjKFvC iXYtuiaaYIEBw5Tj7U9IY0QhUCAmVyZQ40PzU= MIME-Version: 1.0 Received: by 10.239.185.78 with SMTP id b14mr567093hbh.89.1264310935759; Sat, 23 Jan 2010 21:28:55 -0800 (PST) In-Reply-To: References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <5da0588e1001231541l246769eao410c5ea6ccca0de4@mail.gmail.com> <5da0588e1001231615t37c22575uedaae938be40f530@mail.gmail.com> <4B5B94B8.7070509@modulus.org> <5da0588e1001231638i349f8f17t297e970b08825441@mail.gmail.com> <5da0588e1001232017m6c67731fwaa1d71cd86800017@mail.gmail.com> Date: Sun, 24 Jan 2010 00:28:55 -0500 Message-ID: <5da0588e1001232128w5a551674od0805c2ff0b884ad@mail.gmail.com> From: Rich To: jhell Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-fs@freebsd.org Subject: Re: Errors on a file on a zpool: How to remove? 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: Sun, 24 Jan 2010 05:28:57 -0000 On Sun, Jan 24, 2010 at 12:15 AM, jhell wrote: > From what I see and what was already mentioned earlier in this thread is > meta data corruption but the checksum errors do not span across the whole > pool of vdevs. These are, correct me if I am wrong USB mass storage devices > ? SSD ? 1.5T Seagate 7200RPM drives. > In the arrangement of the devices on the system are da2,4,5 on the same hub > and da6,7 on another ? If this is the case you may have consolidated your > errors down to being a USB problem and narrowed down to where they are > connected to. ...no. All five are on the same SATA controller. These behaviors persist independent of which SATA controller they are plugged into, and I've tried all seven in the machine. > What happened to da1,3 ? Were these once connected to the system ? and if so > did you start noticing this problem occur roughly about the same period they > were removed ? da1,3 are being used in another disk pool, and were never a part of this pool. This is not an issue of a faulty SATA controller or SATA drives. This is an issue of "there was a single faulty stick of RAM in the machine". I have sixteen disks in this machine. These three are having issues only on these particular files, and only on these files, not on random portions of the disk. The disks never report read errors - the ZFS layer is what reports them. SMART is not reporting any difficulties in reading any sectors of these disks. I could be mistaken, but I do not believe there to be a faulty controller in play at this time. I've rotated the drives among the spares of the 24 ports on the SATA controller in question, as well as the on-motherboard controller, and this behavior has persisted. - Rich