ZFS: kmem_map too small panic again

Pawel Jakub Dawidek pjd at FreeBSD.org
Fri Apr 27 14:26:35 UTC 2007


On Fri, Apr 27, 2007 at 12:35:35AM +0200, Pawel Jakub Dawidek wrote:
> On Thu, Apr 26, 2007 at 02:33:47PM -0700, Bakul Shah wrote:
> > An update:
> > 
> > I reverted sources to to Apr 24 16:49 UTC and rebuilt the
> > kernel and the bug goes away -- I was able to restore 53GB
> > (840K+ inodes) and do a bunch of du with no problems.
> > 
> > But the bug remains on a kernel with the latest zfs changes.
> > All I have to do run du a couple of times in the restored
> > tree to crash the system.  There is no crash with multiple du
> > on a similarly sized UFS2, only on ZFS.  This is on a
> > Athlon64 X2 Dual Core Processor 3800+ running in 32 bit mode.
> > The exact message is:
> > 
> > panic: kmem_malloc(98304): kmem_map too small: 335478784 total allocated
> 
> I can reproduce it and I'm working on it.

The problem is that kern.maxvnodes are tuned based on vnode+UFS_inode
size. In case of ZFS, the size of vnode+ZFS_znode_dnode+dmu_buf is
larger. As a work-around just decrease kern.maxvnodes to something like
3/4 of the current value.

-- 
Pawel Jakub Dawidek                       http://www.wheel.pl
pjd at FreeBSD.org                           http://www.FreeBSD.org
FreeBSD committer                         Am I Evil? Yes, I Am!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20070427/0a8d2857/attachment.pgp


More information about the freebsd-fs mailing list