From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 20:06:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3C5F16A4CE for ; Mon, 11 Oct 2004 20:06:54 +0000 (GMT) Received: from corbulon.video-collage.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id B75B743D41 for ; Mon, 11 Oct 2004 20:06:53 +0000 (GMT) (envelope-from Mikhail.Teterin@murex.com) Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])i9BK6paB039892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 11 Oct 2004 16:06:52 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) Received: from [127.0.0.1] (mteterin@localhost [127.0.0.1]) i9BK6lFM022348; Mon, 11 Oct 2004 16:06:47 -0400 (EDT) (envelope-from Mikhail.Teterin@murex.com) Message-ID: <416AE7D7.3030502@murex.com> Date: Mon, 11 Oct 2004 16:06:47 -0400 From: Mikhail Teterin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; uk-UA; rv:1.7.2) Gecko/20041006 X-Accept-Language: uk, en-us, en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org, bde@zeta.org.au, dillon@apollo.backplane.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Mailman-Approved-At: Tue, 12 Oct 2004 14:36:20 +0000 Subject: hangs in nbufkv X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 20:06:54 -0000 Hello! While investigating the server's hanging, I noticed some processes in the `nbufkv' state (even a graceful reboot becomes impossible: "some processes would not die..."). Quick search brought up links like: http://lists.freebsd.org/pipermail/freebsd-current/2003-June/004702.html http://docs.freebsd.org/cgi/getmsg.cgi?fetch=56559+0+archive/1999/freebsd-current/19991031.freebsd-current http://docs.freebsd.org/cgi/getmsg.cgi?fetch=406042+0+archive/1999/freebsd-current/19991031.freebsd-current One of our file systems here does, indeed, use large block size (64K, I think, not sure, how to verify it) -- it is used for storing large database dumps. Are the bugs, Bruce and Matt are talking about, supposed to be gone by now (in which case, I can provide more debugging info), or does this remain a "known problem" and I should simply adopt the workaround suggested by Bruce in the first link above -- increase BKVASIZE? Should I also merge the patch posted by Bruce in the last of the links above, or are there good reasons, it is not in the official tree? In the former case, what would anyone need to know to help fix this problem(s)? In the latter -- what is a good BKVASIZE value for an amd64 opteron with 2Gb of memory, intended, primarily, to keep database archives online and handy? Thanks! -mi