Date: Wed, 10 Apr 2002 17:44:47 -0700 From: mki@mozone.net To: Mike Tancsa <mike@sentex.net> Cc: stable@freebsd.org Subject: Re: 4.5-RELEASE panic in getnewvnode() Message-ID: <20020410174447.B18337@cyclonus.mozone.net> In-Reply-To: <5.1.0.14.0.20020410202016.0549f008@192.168.0.12>; from mike@sentex.net on Wed, Apr 10, 2002 at 08:25:46PM -0400 References: <20020410170103.A18337@cyclonus.mozone.net> <5.1.0.14.0.20020410202016.0549f008@192.168.0.12>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Apr 10, 2002 at 08:25:46PM -0400, Mike Tancsa wrote: > At 05:01 PM 4/10/2002 -0700, mki@mozone.net wrote: > >Hi, > > > >We're running 4.5-RELEASE, and can reproduce the following panic by simply > >doing a find / ; both with softupdates on or off. It generally seems to > >crash within /usr/ports. > > Did you try this out on a STABLE box ? I tried it both on a UP and SMP > stable box (find / ;) and it made it through everything. It appears that it's related to the fact that I was setting nmbclusters to 64000 during boot, when we reduced this to 60000, the problem was addressed. I wonder if raising the kva space would address this (ie be able to have that high (or even higher) nmbclusters) while not causing the machine to panic when it's doing things like a find. -mk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020410174447.B18337>