From owner-freebsd-current@FreeBSD.ORG  Tue Nov  3 17:36:21 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 439121065672
	for <freebsd-current@FreeBSD.org>; Tue,  3 Nov 2009 17:36:21 +0000 (UTC)
	(envelope-from weldon@excelsusphoto.com)
Received: from mx0.excelsus.net (emmett.excelsus.com [74.93.113.252])
	by mx1.freebsd.org (Postfix) with ESMTP id CE1968FC17
	for <freebsd-current@FreeBSD.org>; Tue,  3 Nov 2009 17:36:20 +0000 (UTC)
Received: (qmail 66617 invoked by uid 89); 3 Nov 2009 17:36:18 -0000
Received: from unknown (HELO localhost) (127.0.0.1)
	by localhost.excelsus.com with SMTP; 3 Nov 2009 17:36:18 -0000
Date: Tue, 3 Nov 2009 12:36:18 -0500 (EST)
From: Weldon S Godfrey 3 <weldon@excelsusphoto.com>
X-X-Sender: weldon@emmett.excelsus.com
To: Gavin Atkinson <gavin@FreeBSD.org>
In-Reply-To: <alpine.BSF.2.00.0911031033120.80499@emmett.excelsus.com>
Message-ID: <alpine.BSF.2.00.0911031234210.80499@emmett.excelsus.com>
References: <alpine.BSF.2.00.0911020747560.80499@emmett.excelsus.com>
	<1257185816.44755.29.camel@buffy.york.ac.uk>
	<alpine.BSF.2.00.0911030819410.36102@emmett.excelsus.com>
	<1257261214.98619.92.camel@buffy.york.ac.uk>
	<alpine.BSF.2.00.0911031033120.80499@emmett.excelsus.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Tue, 03 Nov 2009 18:11:37 +0000
Cc: freebsd-current@FreeBSD.org
Subject: Re: FreeBSD 8.0 - network stack crashes?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Nov 2009 17:36:21 -0000



If memory serves me right, sometime around 10:43am, Weldon S Godfrey 3 told me:

>
>
> If memory serves me right, sometime around 3:13pm, Gavin Atkinson told me:
>
>> OK, at least we've figured out what is going wrong then.  As a
>> workaround to get the machine to stay up longer, you should be able to
>> set kern.ipc.nmbclusters=256000 in /boot/loader.conf -but hopefully we
>> can resolve this soon.
>>

I upped it to 256K.  What I am trying to wrap my head around is how it was 
working somewhat for so long at 24K, but it got to near 65K before I 
rebooted it with the higher setting.   Or did I reboot too early?  Is 
there any cleanup that isn't triggered intil it reaches max nmbclusters? 
I am trying to see if anything on our network has changed to cause this to 
become cronic.