From owner-freebsd-fs@FreeBSD.ORG Sat Jan 23 12:43:43 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 B7D92106568D for ; Sat, 23 Jan 2010 12:43:43 +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 4B9738FC27 for ; Sat, 23 Jan 2010 12:43:42 +0000 (UTC) Received: by fxm26 with SMTP id 26so2020671fxm.13 for ; Sat, 23 Jan 2010 04:43:42 -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 :content-transfer-encoding; bh=3qCGqSqYnHZhYELkbzBFumqRelk727xHoFqaLUpp+qY=; b=Hc7Uc5piY2GciRCy6BtsgO+cIAhczEdlB1L/znffSE0ROOUWsVg8IRbta2c9fv09tU M5O2XMscjRLeF09HJBlXA9hqvu0tHTIe6L2QF+FZ9+Mbd8114/KOgS2wZZwAMewTKBO+ R3l6cNHDSQC4URgMoS4RiB2Lyg++w/hMUP+H4= 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:content-transfer-encoding; b=qXGMjALopFkychQIhBrovpkxRXfTcWhqIPQzAjpC8VBBkUlzLMSYQPBOOh+LMULVVq Un5nypKUTjS+yvtsLKlJk4QiI0MvdGZYkdzbmIrvZC8LviHOf0gFz8LuIQttKlM0pBya uwri1N9W6wsVkpruLomstSjzyQD1/4Ik/778M= MIME-Version: 1.0 Received: by 10.239.187.139 with SMTP id l11mr480113hbh.96.1264250615907; Sat, 23 Jan 2010 04:43:35 -0800 (PST) In-Reply-To: <4B5AE8D7.9000103@modulus.org> References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> <4B5AE8D7.9000103@modulus.org> Date: Sat, 23 Jan 2010 07:43:35 -0500 Message-ID: <5da0588e1001230443r1fee3b45o906690bc0115bb4e@mail.gmail.com> From: Rich To: Andrew Snow Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: Sat, 23 Jan 2010 12:43:43 -0000 zpool clear always clears the checksum column whenever I run it. Then, as soon as I touch those files again, or run a scrub, the checksum error numbers tick up on those three disks, and those entries appear in /var/log/messages. - Rich On Sat, Jan 23, 2010 at 7:17 AM, Andrew Snow wrote: > Rich wrote: >> >> Scrubbing repeatedly does nothing to remove the note about that error, >> and I'd rather like to avoid trying to recreate a 7TB pool. > > If you have bad hardware, its quite possible for ZFS to get itself into a > state that it cannot repair itself. =A0The claim about "never needs fsck"= only > applies if the hardware is doing what is expected of it. This especially > goes for a pool with zero redundancy, like yours. > > Its pretty good that ZFS can report the checksum failures where with othe= r > filesystems wouldn't even know something's wrong until it starts returnin= g > garbled data or crashes the whole kernel. > > I presume you have already tried "zpool clear" ? > > - Andrew > > --=20 Life is a yo-yo, and mankind ties knots in the string.