From owner-freebsd-fs@FreeBSD.ORG Mon Apr 23 10:56:17 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B16816A403 for ; Mon, 23 Apr 2007 10:56:17 +0000 (UTC) (envelope-from staalebk@ifi.uio.no) Received: from smtp.bluecom.no (smtp.bluecom.no [193.75.75.28]) by mx1.freebsd.org (Postfix) with ESMTP id 1C6DD13C46A for ; Mon, 23 Apr 2007 10:56:17 +0000 (UTC) (envelope-from staalebk@ifi.uio.no) Received: from eschew.pusen.org (unknown [193.69.145.10]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.bluecom.no (Postfix) with ESMTP id CEABB16FC18 for ; Mon, 23 Apr 2007 12:56:15 +0200 (CEST) Received: from chiller by eschew.pusen.org with local (Exim 4.50) id 1HfwDT-00045W-MG for freebsd-fs@FreeBSD.org; Mon, 23 Apr 2007 12:56:19 +0200 Date: Mon, 23 Apr 2007 12:56:19 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: freebsd-fs@FreeBSD.org Message-ID: <20070423105619.GA14400@eschew.pusen.org> References: <46205338.3090803@barryp.org> <20070415111955.GB16971@garage.freebsd.pl> <46224706.4010704@barryp.org> <20070422212019.GJ52622@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20070422212019.GJ52622@garage.freebsd.pl> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: Re: ZFS raidz device replacement problem 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: Mon, 23 Apr 2007 10:56:17 -0000 On 2007-04-22 at 23:20, Pawel Jakub Dawidek wrote: > I just committed a fix for 'zpool status -v'. It should now show > actually file names if corruption is related to file's data. I tried the fix and it did work. However, when I deleted the file and restored it from backup it still showed that the pool had one error. (Showing only 0x62b as filename again). Shouldn't ZFS automatically clear the error when deleting the file? I tried exporting and importing the pool, didn't change anything, I then ran a scrub and it fixed it: scrub: scrub completed with 0 errors on Mon Apr 23 09:45:36 2007 errors: No known data errors I would have preferred if I didn't have to scrub the pool, would it be hard to fix it on delete? thanks! -- Ståle Kristoffersen staalebk@ifi.uio.no