From owner-freebsd-fs@FreeBSD.ORG Wed Oct 14 16:47:39 2009 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 806301065670; Wed, 14 Oct 2009 16:47:39 +0000 (UTC) (envelope-from solon@pyro.de) Received: from srv23.fsb.echelon.bnd.org (mail.pyro.de [83.137.99.96]) by mx1.freebsd.org (Postfix) with ESMTP id 8F8E38FC15; Wed, 14 Oct 2009 16:47:37 +0000 (UTC) Received: from port-87-193-183-44.static.qsc.de ([87.193.183.44] helo=flash.home) by srv23.fsb.echelon.bnd.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69 (FreeBSD)) (envelope-from ) id 1My70e-00041m-Fe; Wed, 14 Oct 2009 18:47:36 +0200 Date: Wed, 14 Oct 2009 18:47:31 +0200 From: Solon Lutz X-Mailer: The Bat! (v3.99.25) Professional Organization: pyro.labs berlin X-Priority: 3 (Normal) Message-ID: <473227349.20091014184731@pyro.de> To: Pawel Jakub Dawidek , freebsd-fs@FreeBSD.ORG In-Reply-To: <673550066.20091013133544@pyro.de> References: <20091004185738.GI1660@garage.freebsd.pl> <165582258.20091012155536@pyro.de> <20091012193636.GC1762@garage.freebsd.pl> <756365088.20091013005202@pyro.de> <20091013055754.GA3197@garage.freebsd.pl> <90685589.20091013092418@pyro.de> <20091013072712.GA1597@garage.freebsd.pl> <12910471099.20091013095322@pyro.de> <20091013075511.GC1597@garage.freebsd.pl> <1433853337.20091013100348@pyro.de> <20091013082116.GE1597@garage.freebsd.pl> <673550066.20091013133544@pyro.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: -0.1 (/) X-Spam-Report: Spam detection software, running on the system "srv23.fsb.echelon.bnd.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: >>> >> > As I understand the values 13462283 and 13462284 were showing errors? >>> >> > Yes, just try to import the pool and set vfs.zfs.maxtxg back to zero >>> >> > afterwards. >>> >> 13462283 and 13462284 were showing errors. >>> >> vfs.zfs.maxtxg was at -1 before I changed it. [...] Content analysis details: (-0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.3 PLING_QUERY Subject has exclamation mark and question mark X-Spam-Flag: NO Cc: Subject: Re: Help needed! ZFS I/O error recovery? 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, 14 Oct 2009 16:47:39 -0000 >>> >> > As I understand the values 13462283 and 13462284 were showing errors? >>> >> > Yes, just try to import the pool and set vfs.zfs.maxtxg back to zero >>> >> > afterwards. >>> >> 13462283 and 13462284 were showing errors. >>> >> vfs.zfs.maxtxg was at -1 before I changed it. >>> > So does it work now? >>> radium# zpool import -f temp >>> cannot iterate filesystems: I/O error >>> radium# ll /temp/ >>> ls: backup: Input/output error >>> total 9 >>> drwxr-xr-x 2 root wheel 2 May 16 2007 audio >>> drwxr-xr-x 2 root wheel 2 May 16 2007 misc >>> drwxr-xr-x 2 root wheel 2 May 16 2007 video >>> drwxr-xr-x 8 dhcpd dhcpd 11 Jul 8 10:36 www >>> radium# ll /temp/audio/ >>> total 0 >>> radium# ll /temp/misc/ >>> total 0 >>> radium# zfs unmount temp >>> cannot iterate filesystems: I/O error >> Can you show 'zpool status'? >> It might be worth trying to go even more in the past with maxtxg. > sysctl vfs.zfs.maxtxg=13462260 > pool: temp > state: ONLINE > status: One or more devices has experienced an error resulting in data > corruption. Applications may be affected. > action: Restore the file in question if possible. Otherwise restore the > entire pool from backup. > see: http://www.sun.com/msg/ZFS-8000-8A > scrub: none requested > config: > NAME STATE READ WRITE CKSUM > temp ONLINE 0 0 9 > da0 ONLINE 0 0 36 > errors: Permanent errors have been detected in the following files: > temp:<0x0> > temp:<0x49681> > temp:<0x499a4> > temp:<0x495fd> > temp/space1:<0x0> > temp/space2:<0x0> > temp/space3:<0x0> > temp/space4:<0x0> > temp/space5:<0x0> I just tried it with more TXGs, even with a jump of -300, but it always gives an "cannot iterate filesystems: I/O error" error if I try to import the pool. Also because of mounting the pool, the TXg has gone up to 13445935 from initially 13462284. solon