From owner-freebsd-fs@FreeBSD.ORG Sat Aug 30 22:14:26 2014 Return-Path: Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3658DA43 for ; Sat, 30 Aug 2014 22:14:26 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 184551FD1 for ; Sat, 30 Aug 2014 22:14:26 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7UMEPWb034590 for ; Sat, 30 Aug 2014 22:14:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 Date: Sat, 30 Aug 2014 22:14:25 +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: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: In Discussion X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Aug 2014 22:14:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112 Peter Wemm changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter@FreeBSD.org --- Comment #5 from Peter Wemm --- If you look at the whole comment for one of the assertions you disabled: /* * lhr_pad was previously used for the next leaf in the leaf * chain. There should be no chained leafs (as we have removed * support for them). */ ASSERT0(l->l_phys->l_hdr.lh_pad1); Or looking at the annotation: 168404 pjd /* 168404 pjd * lhr_pad was previously used for the next leaf in the leaf 168404 pjd * chain. There should be no chained leafs (as we have removed 168404 pjd * support for them). 168404 pjd */ 240415 mm ASSERT0(l->l_phys->l_hdr.lh_pad1); One of those is the initial commit: ------------------------------------------------------------------------ r168404 | pjd | 2007-04-05 18:09:06 -0700 (Thu, 05 Apr 2007) | 11 lines Please welcome ZFS - The last word in file systems. ZFS file system was ported from OpenSolaris operating system. The code in under CDDL license. ------------------------------------------------------------------------ The second is: ------------------------------------------------------------------------ r240415 | mm | 2012-09-12 11:05:43 -0700 (Wed, 12 Sep 2012) | 21 lines Merge recent zfs vendor changes, sync code and adjust userland DEBUG. ------------------------------------------------------------------------ The change is just a syntax one: - ASSERT3U(l->l_phys->l_hdr.lh_pad1, ==, 0); + ASSERT0(l->l_phys->l_hdr.lh_pad1); So.. ever since ZFS existed in FreeBSD, that field should be zero, on disk. You are tripping those asserts because it isn't the case on your machine. This suggests to me that you've either got a very old file system that pre-dates freebsd, or you've got some evil on-disk corruption. I suspect the latter. If this was my machine, I'd be contemplating a backup/restore. I see from the disk sizes you may have a lot of data, but that's what I would be doing. I also see the stack traces come from the zfs de-dupe code. There are a great number of people who have a very dim view of that code, even the authors apologized for it. If it were my machine, I would be turning off dedup immediately, if not sooner. -- You are receiving this mail because: You are the assignee for the bug.