Date: Tue, 16 Mar 2004 15:18:37 -0500 From: Sven Willenberger <sven@dmv.com> To: freebsd-current@freebsd.org Subject: Re: kmem_map too small, revisited Message-ID: <1079468317.23554.98.camel@lanshark.dmv.com> In-Reply-To: <1079452815.23554.69.camel@lanshark.dmv.com> References: <1079446098.23554.49.camel@lanshark.dmv.com> <20040316152013.GA82071@walton.maths.tcd.ie> <1079452815.23554.69.camel@lanshark.dmv.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2004-03-16 at 11:00, Sven Willenberger wrote:
> On Tue, 2004-03-16 at 10:20, David Malone wrote:
> > On Tue, Mar 16, 2004 at 09:08:18AM -0500, Sven Willenberger wrote:
> > > Where should I begin to better diagnose what exactly is going on here?
> >
> > I can suggest two ways. The first is to record the output of "vmstat
> > -m" every 5 minutes from when the machine boots until it dies. If
> > something is consuming all your kernel memory, this may tell us
> > what subsystem it is.
>
> I will get that started on one of the boxes ASAP.
>
In comparing the vmstat -m output from a machine that has recently
rebooted and one that has been up for a few weeks (which is usually
about the max before the panic/reboot) I did notice an abnormally high
(in comparison) value of cred:
> uptime
3:11PM up 26 days, 2:28, 1 user, load averages: 0.00, 0.00, 0.00
> sysctl kern.malloc
kern.malloc:
Type InUse MemUse HighUse Requests Size(s)
.
.
.
cred1445117180640K 180641K 9036491 128
.
.
.
versus:
> uptime
3:13PM up 7 days, 1:38, 1 user, load averages: 1.49, 1.02, 0.74
> sysctl kern.malloc
kern.malloc:
Type InUse MemUse HighUse Requests Size(s)
.
.
.
cred 326 41K 49K 6666888 128
.
.
.
What exactly is "cred" and how would I go about finding out a) if that
first set of numbers is completely out of line and b) what is causing it
to go so high if it is in fact out of whack.
Sven
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1079468317.23554.98.camel>