Date: Thu, 3 May 2007 22:28:50 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen <staalebk@ifi.uio.no> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org Subject: Re: ZFS raidz device replacement problem Message-ID: <20070503202850.GA28808@eschew.pusen.org> In-Reply-To: <20070503191139.GD7177@garage.freebsd.pl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <pool>' 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070503202850.GA28808>