From owner-freebsd-fs@FreeBSD.ORG Wed Feb 6 10:06:52 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 3EB3E16A468; Wed, 6 Feb 2008 10:06:52 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id EED0513C458; Wed, 6 Feb 2008 10:06:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id D69972082; Wed, 6 Feb 2008 11:06:42 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id C7D8A2049; Wed, 6 Feb 2008 11:06:42 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id ADB9384493; Wed, 6 Feb 2008 11:06:42 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jeremy Chadwick References: <47A73C8D.3000107@skyrush.com> <86prvby5o1.fsf@ds4.des.no> <47A864D9.4060504@skyrush.com> <864pcnxz8f.fsf@ds4.des.no> <47A88ADE.7050503@skyrush.com> <86abmfwc6h.fsf@ds4.des.no> <20080205192137.GA66362@eos.sc1.parodius.com> Date: Wed, 06 Feb 2008 11:06:42 +0100 In-Reply-To: <20080205192137.GA66362@eos.sc1.parodius.com> (Jeremy Chadwick's message of "Tue\, 5 Feb 2008 11\:21\:37 -0800") Message-ID: <86prvav1ot.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org Subject: Re: Forcing full file read in ZFS even when checksum error encountered 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: Wed, 06 Feb 2008 10:06:52 -0000 Jeremy Chadwick writes: > I realise I classify pretty much everything as "priority 0" (of utmost > importance), but there doesn't appear to be any indication of anyone > caring about this problem. Most likely, nobody with the ability to find and fix the cause of your problem has been able to reproduce it. It's really hard to fix a bug you can't reproduce; you're basically flying blind, unless the person who reported the issue is very experienced and can cooperate in diagnosing the problem (which is very rare). > I want to do more to help, but I don't know what I *can* do, besides > offer to buy people identical hardware for attempted reproduction, or > put up a test box with serial console access for developers to beat up > on. Several developers already *have* identical hardware, or nearly so. (speaking for myself, all my Seagate disks are dead, and I use Western Digital exclusively these days, as they tend to live longer in my experience; sometimes they don't even fail until *after* the warranty runs out!) > | Making life hard for others since 1977. PGP: | 4BD6C0C= B | Ooh, a kindred spirit! :) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no