From owner-freebsd-fs@FreeBSD.ORG Wed Apr 18 11:01:12 2007 Return-Path: X-Original-To: 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 C132F16A400 for ; Wed, 18 Apr 2007 11:01:12 +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 87CEA13C43E for ; Wed, 18 Apr 2007 11:01:12 +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 B8CCF12CDFF for ; Wed, 18 Apr 2007 12:41:32 +0200 (CEST) Received: from chiller by eschew.pusen.org with local (Exim 4.50) id 1He7bn-0002Yc-Bf for fs@freebsd.org; Wed, 18 Apr 2007 12:41:55 +0200 Date: Wed, 18 Apr 2007 12:41:55 +0200 From: =?iso-8859-1?Q?St=E5le?= Kristoffersen To: fs@freebsd.org Message-ID: <20070418104155.GA31727@eschew.pusen.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: ZFS + replacing failing hard-drive. 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: Wed, 18 Apr 2007 11:01:12 -0000 Hi! I have been testing ZFS on my fileserver. The data I had in the zpool is not that important so I do not have redundancy. Unfortunately I got a bad hard-drive: Apr 13 22:02:44 fs root: ZFS: vdev I/O failure, zpool=stash path=/dev/ad14s1d offset=336216064000 size=131072 error=5 Apr 13 22:02:56 fs kernel: ad14: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3013311 I therefor bought a new drive and used dd_rescue to copy the salvageable blocks to the new disk. Booting up and things are looking good, no more DMA-errors and things seems to work. The only problem is that the blocks (24) that could not be copied produce CKSUM errors. This is perfect, but I now wants to delete the files that are touched by the problem, but 'zpool status -v' do not give me a path like in the zfs-handbook: errors: Permanent errors have been detected in the following files: stash/TV:<0x62b> How can I figure out what files are affected? Is there any way to fix this without rebuilding the pool? -- Ståle Kristoffersen staalebk@ifi.uio.no