From owner-freebsd-fs@FreeBSD.ORG Thu May 3 20:28:47 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 BC34016A406 for ; Thu, 3 May 2007 20:28:47 +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 5F88313C447 for ; Thu, 3 May 2007 20:28:47 +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 0315A16F7E6; Thu, 3 May 2007 22:28:46 +0200 (CEST) Received: from chiller by eschew.pusen.org with local (Exim 4.50) id 1Hjhv1-0001lA-01; Thu, 03 May 2007 22:28:51 +0200 Date: Thu, 3 May 2007 22:28:50 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: Pawel Jakub Dawidek Message-ID: <20070503202850.GA28808@eschew.pusen.org> References: <46205338.3090803@barryp.org> <20070415111955.GB16971@garage.freebsd.pl> <46224706.4010704@barryp.org> <20070422212019.GJ52622@garage.freebsd.pl> <20070423105619.GA14400@eschew.pusen.org> <20070503191139.GD7177@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: <20070503191139.GD7177@garage.freebsd.pl> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-fs@FreeBSD.org 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: Thu, 03 May 2007 20:28:47 -0000 On 2007-05-03 at 21:11, Pawel Jakub Dawidek wrote: > On Mon, Apr 23, 2007 at 12:56:19PM +0200, St?le Kristoffersen wrote: > > 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? > > 'zpool clear ' should do the trick. I forgot to mention that I did try that, and that seems like it only clears the numbers. -- Ståle Kristoffersen staalebk@ifi.uio.no