From owner-freebsd-fs@FreeBSD.ORG  Sat Aug 30 22:51:16 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1550852A
 for <freebsd-fs@FreeBSD.org>; Sat, 30 Aug 2014 22:51:16 +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 F14361340
 for <freebsd-fs@FreeBSD.org>; Sat, 30 Aug 2014 22:51:15 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7UMpFNI099018
 for <freebsd-fs@FreeBSD.org>; Sat, 30 Aug 2014 22:51:15 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:51:16 +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: 
Message-ID: <bug-186112-3630-4MumhH4LDb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-186112-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-186112-3630@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Aug 2014 22:51:16 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186112

--- Comment #7 from Peter Wemm <peter@FreeBSD.org> ---
Out of curiosity, what does "zpool status -D poolname" show?

http://serverfault.com/questions/533877/how-large-is-my-zfs-dedupe-table-at-the-moment

You might be burning a significant chunk of ARC metadata space to hold the
dedupe table in memory.

If I had to guess at this point, I would guess that there are a couple of
corrupt records in the on-disk dedup table for one or more of your data sets. 
Since this is an old pool, there's been plenty of opportunities over the years
for this to accumulate while zfs support matured.

>From your comment, it sounds like you have 1TB of data spread over a pool made
of 2TB disks?  Is that deduplicated?  Is one of the drives a spare? (if so, can
you take the spare offline and make a pool on it to facilitate a dump/restore?)

-- 
You are receiving this mail because:
You are the assignee for the bug.