Date: Tue, 3 Nov 2009 12:36:18 -0500 (EST) From: Weldon S Godfrey 3 <weldon@excelsusphoto.com> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: FreeBSD 8.0 - network stack crashes? Message-ID: <alpine.BSF.2.00.0911031234210.80499@emmett.excelsus.com> In-Reply-To: <alpine.BSF.2.00.0911031033120.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0911031234210.80499>