From owner-freebsd-bugs@FreeBSD.ORG Tue Sep 30 01:06:53 2014 Return-Path: Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F904DCD for ; Tue, 30 Sep 2014 01:06:53 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 76C4418C for ; Tue, 30 Sep 2014 01:06:53 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8U16rq6080152 for ; Tue, 30 Sep 2014 01:06:53 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193875] [zfs] [panic] [reproducable] zfs/space_map.c: solaris assert: sm->sm_space + size <= sm->sm_size Date: Tue, 30 Sep 2014 01:06:53 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: delphij@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2014 01:06:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D193875 --- Comment #5 from Xin LI --- (In reply to Palle Girgensohn from comment #4) > I did not try a newly created pool, it is a large pool with data, one of = two > redundant systems where we use zfs send | ssh | zfs recv to keep them in > sync. The other machine is still on 9.3, and we got this problem after > updating one system to 10.0. So, we cannot really upgrade just yet. Also,= it > shouln't present such a big problem just running an old version...? Since you haven't upgraded the pool, will it be possible for you to downgra= de your kernel/world and see if you can reproduce the problem? > But as you say, there seems to something fishy with the pool, and maybe > there is nothing wrong with the kernel itself.=20 >=20 > Are you sure there are no other ways to fix this but to recreate the pool? > Thera are just Terabytes of data, it will take a week... :-/ Yeah I know =EF=BC=9A=EF=BC=88 > is there no zdb magic or zpool export + scrub + zpool import ditto with > vfs.zfs.recover =3D1 that could help? Unfortunately, space map corruptions are fatal currently. In the future ma= ybe we can implement a tool that traverses all data and rebuild the space map f= rom that, but it's not trivial... --=20 You are receiving this mail because: You are the assignee for the bug.=