From owner-freebsd-stable@FreeBSD.ORG  Tue Dec 16 16:22:52 2008
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 298F91065673
	for <stable@freebsd.org>; Tue, 16 Dec 2008 16:22:52 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84])
	by mx1.freebsd.org (Postfix) with ESMTP id D908C8FC08
	for <stable@freebsd.org>; Tue, 16 Dec 2008 16:22:51 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by kabab.cs.huji.ac.il with esmtp id 1LCch8-000G0M-Q2
	for stable@freebsd.org; Tue, 16 Dec 2008 18:22:50 +0200
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: stable@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 16 Dec 2008 18:22:50 +0200
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1LCch8-000G0M-Q2@kabab.cs.huji.ac.il>
Cc: 
Subject: more zfs/nfs panics
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Dec 2008 16:22:52 -0000

Hi,
I'm trying to tar a rather big directory via nfs (some 800gb), it
has many subdirectories, some of them with many files (close to 10^6 :-)

just before the server panics, the tar (on the client) starts complaining 
about lost
files, or permition denied, but not in the pathological directories.
panic: kmem_malloc(-1661382656): kmem_map too small: 645009408 total allocated
cpuid = 3
KDB: enter: panic
[thread pid 881 tid 100112 ]
Stopped at      kdb_enter_why+0x3d:     movq    $0,0x5ef3e8(%rip)
db> tr
Tracing pid 881 tid 100112 td 0xffffff0004ba2000
kdb_enter_why() at kdb_enter_why+0x3d
panic() at panic+0x17b
kmem_malloc() at kmem_malloc+0x565
uma_large_malloc() at uma_large_malloc+0x4a
malloc() at malloc+0xd7
nfsrv_readdir() at nfsrv_readdir+0x4e1
nfssvc() at nfssvc+0x400
syscall() at syscall+0x1bb
Xfast_syscall() at Xfast_syscall+0xab
--- syscall (155, FreeBSD ELF64, nfssvc), rip = 0x8006885cc, rsp = 
0x7fffffffea28, rbp = 0 ---

I have increased 
	vm.kmem_size_max="1024M"
	vm.kmem_size="1024M"
	vfs.zfs.arc_max="800M"
it just seems to delay the panic though, it smells like some memory leak ...

the host is running amd64 quad core, 7.1-prerelease and 8GB.

danny