Date: Sat, 30 Aug 2014 22:51:16 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-fs@FreeBSD.org Subject: [Bug 186112] [zfs] [panic] ZFS Panic/Solaris Assert/zap.c:479 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-186112-3630-4MumhH4LDb>