From owner-freebsd-stable@FreeBSD.ORG Mon May 2 14:51:46 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D97A6106564A for ; Mon, 2 May 2011 14:51:46 +0000 (UTC) (envelope-from O.Seibert@cs.ru.nl) Received: from rustug.science.ru.nl (rustug.science.ru.nl [131.174.16.158]) by mx1.freebsd.org (Postfix) with ESMTP id 5C2AF8FC1A for ; Mon, 2 May 2011 14:51:45 +0000 (UTC) Received: from kookpunt.science.ru.nl (kookpunt.science.ru.nl [131.174.30.61]) by rustug.science.ru.nl (8.13.7/5.31) with ESMTP id p42EWXwq012551 for ; Mon, 2 May 2011 16:32:33 +0200 (MEST) Received: from twoquid.cs.ru.nl (twoquid.cs.ru.nl [131.174.142.38]) by kookpunt.science.ru.nl (8.13.7/5.31) with ESMTP id p42EWTcj020870; Mon, 2 May 2011 16:32:29 +0200 (MEST) Received: by twoquid.cs.ru.nl (Postfix, from userid 4100) id 8C5732E04B; Mon, 2 May 2011 16:32:30 +0200 (CEST) Date: Mon, 2 May 2011 16:32:30 +0200 From: Olaf Seibert To: freebsd-stable@freebsd.org Message-ID: <20110502143230.GW6733@twoquid.cs.ru.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) X-Spam-Score: -1.799 () ALL_TRUSTED,BAYES_50 X-Scanned-By: MIMEDefang 2.63 on 131.174.30.61 Subject: Automatic reboot doesn't reboot X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 May 2011 14:51:46 -0000 Hi, I have a FreeBSD/amd64 8.2 server that has a few ZFS file systems served over NFS. It has 8 GB of memory. There are 6 disks of 1,5 TB each forming a pool with raidz2. >From time to time it crashes with some stack backtrace (included below). This already happened before the upgrade to 8.2. Now a crash of a file server is annoying, but if it reboots automatically, there is just a few minutes of downtime (most of it is even spent by the BIOS before it gets to boot the OS). However, it doesn't automatically reboot in 15 seconds, as promised. It just sits there the whole weekend, until I log onto the IPMI console and press the virtual reset button. This was visible before I did that (4-finger copy): panic: kmem_alloc(131072): kmem_map too small: 3428782080 total allocated cpuid = 0 KDB: stack backtrace: #0 0xffffffff805f4e0e at kdb_backtrace+0x5e #1 0xffffffff805c2d07 at panic+0x187 #2 0xffffffff80816830 at kmem_alloc+0 #3 0xffffffff8080e3ba at uma_large_malloc+0x4a #4 0xffffffff805b0167 at malloc+0xd7 #5 0xffffffff80e87849 at zil_lwb_write_start+0x289 #6 0xffffffff80e87b92 at zil_commit+0x242 #7 0xffffffff80ea035d at zfs_sync+0xcd #8 0xffffffff8065431a at sync_fsync+0x16a #9 0xffffffff806524be at sync_vnode+0x15e #10 0xffffffff806527b1 at sched_sync+0x1d1 #11 0xffffffff805994f8 at fork_exit+0x118 #11 0xffffffff8089547e at fork_trampoline+0xe Uptime: 11d12h56m20s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort and that is where it sat all weekend... Why doesn't the promised reboot happen? The kernel was still the GENERIC one as distributed with 8.2. Because of the reboot it will now be the stripped down one that I compiled myself. There is some tuning in /boot/loader.conf from previous attempts tune to avoid crashes. vm.kmem_size="16G" vfs.zfs.arc_max="4G" Is that still useful, or does it harm by now? Real memory is 8 GB. I note that if I look with sysctl, I see vm.kmem_size: 3739230208 vfs.zfs.arc_max: 2665488384 which doesn't seem to match these attempted settings. -Olaf. -- Pipe rene = new PipePicture(); assert(Not rene.GetType().Equals(Pipe));