From owner-freebsd-current@FreeBSD.ORG Tue Oct 2 17:04:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEC0416A417 for ; Tue, 2 Oct 2007 17:04:24 +0000 (UTC) (envelope-from brooks@illuminati.org) Received: from zmail.illuminati.org (mail.illuminati.org [70.42.141.33]) by mx1.freebsd.org (Postfix) with ESMTP id B6C4313C448 for ; Tue, 2 Oct 2007 17:04:24 +0000 (UTC) (envelope-from brooks@illuminati.org) Received: from localhost (localhost.localdomain [127.0.0.1]) by zmail.illuminati.org (Postfix) with ESMTP id 448A716C86E0 for ; Tue, 2 Oct 2007 10:04:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from zmail.illuminati.org ([127.0.0.1]) by localhost (zmail.illuminati.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIRf2eYK+dvi for ; Tue, 2 Oct 2007 10:04:12 -0700 (PDT) Received: from zmail.illuminati.org (zmail.illuminati.org [10.32.1.33]) by zmail.illuminati.org (Postfix) with ESMTP id 0F16316C86DE for ; Tue, 2 Oct 2007 10:04:12 -0700 (PDT) Date: Tue, 2 Oct 2007 10:04:12 -0700 (PDT) From: Brooks Talley To: freebsd-current Message-ID: <7344605.82541191344652015.JavaMail.root@zmail.illuminati.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [67.168.65.79] Subject: ZFS corrupting data, even just sitting idle X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Oct 2007 17:04:25 -0000 Hi, everyone. I'm running 7.0-current amd64, built from CVS on September 12. I've got a 4.5TB ZFS array across 8 750GB drives in a RAIDZ1 + hotspare configuration. It's corrupting data even just sitting at idle with no access at all. I had loaded it up with about 4TB of data several weeks ago, then noticed that a zpool status showed checksum errors about a week ago. I ran a scrub and it turned 122 errors affecting about 20 files. The errors were spread across the physical disks pretty evenly, so it didn't seem like one bad drive. I left for vacation and unplugged the network from the machine to ensure that there would be no access to the disk. There are no cron jobs or anything else running locally that so much as touch the zpool. Upon returning, I ran a zpool scrub and it found an additional 116 checksum errors in another 17 files, also evenly spread across the physical drives. The system is running a Supermicro motherboard, Supermicro AOC-SAT-MV8 SATA card, and WD 750GB drives. 2GB memory, no real apps running, just storage. Anyone seen anything like this? It's a bit of a concern. Thanks -Brooks