From owner-freebsd-fs@FreeBSD.ORG Wed Oct 14 23:11:44 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 741581065679; Wed, 14 Oct 2009 23:11:43 +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 0B81A8FC12; Wed, 14 Oct 2009 23:11:43 +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 1MyD0N-0004mU-1U; Thu, 15 Oct 2009 01:11:42 +0200 Date: Thu, 15 Oct 2009 01:11:37 +0200 From: Solon Lutz X-Mailer: The Bat! (v3.99.25) Professional Organization: pyro.labs berlin X-Priority: 3 (Normal) Message-ID: <572088116.20091015011137@pyro.de> To: Pawel Jakub Dawidek , freebsd-fs@FreeBSD.ORG In-Reply-To: <20091014210528.GC1727@garage.freebsd.pl> References: <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> <473227349.20091014184731@pyro.de> <20091014210528.GC1727@garage.freebsd.pl> 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: >> 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. [...] 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 23:11:44 -0000 >> 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. > We can try to turn off checksum verification entirely, but it will most > likely just panic your system. > If you want to do this, edit > sys/cddl/contrib/opensolaris/uts/common/fs/zfs/sys/spa.h file and change > ZIO_CHECKSUM_EQUAL() macro to something like this: > #define ZIO_CHECKSUM_EQUAL(zc1, zc2) (1) Yes, it paniced as soon as I tried zpool import. Can you tell where ZFS is taking the information from, that there are I/O errors? Is this based on checksums or is there some kind of I/O-error-flag? solon