From owner-freebsd-fs@FreeBSD.ORG Sat Jan 23 12:17:55 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 32FAB106568D for ; Sat, 23 Jan 2010 12:17:55 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (email.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id E81A48FC13 for ; Sat, 23 Jan 2010 12:17:54 +0000 (UTC) Received: by email.octopus.com.au (Postfix, from userid 1002) id AFC645CB8E9; Sat, 23 Jan 2010 22:53:45 +1100 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: * X-Spam-Status: No, score=1.9 required=10.0 tests=ALL_TRUSTED, FH_DATE_PAST_20XX autolearn=no version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.static.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 523225CB91A; Sat, 23 Jan 2010 22:53:41 +1100 (EST) Message-ID: <4B5AE8D7.9000103@modulus.org> Date: Sat, 23 Jan 2010 23:17:27 +1100 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Rich , freebsd-fs@freebsd.org References: <5da0588e1001222223m773648am907267235bdcf882@mail.gmail.com> <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> In-Reply-To: <5da0588e1001230014k1b8a32f8v42046497265429ed@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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:17:55 -0000 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. The 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 other filesystems wouldn't even know something's wrong until it starts returning garbled data or crashes the whole kernel. I presume you have already tried "zpool clear" ? - Andrew