Date: Mon, 17 Mar 2003 20:26:36 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "John Stockdale" <jstockdale@stanford.edu> Cc: freebsd-current@FreeBSD.ORG Subject: Re: mdconfig/mdmfs problems -> kernel panic Message-ID: <30786.1047929196@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 17 Mar 2003 10:57:50 PST." <000b01c2ecb7$1c089510$3d2c0c80@quenya>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <000b01c2ecb7$1c089510$3d2c0c80@quenya>, "John Stockdale" writes:
>OS: FreeBSD 5.0-CURRENT, JPSNAP20030314
>
>I'm running a Dual Xeon system with 1GB DDRRAM, and trying to create a
>ram disk to compile under, specifically to compile the kernel.
>
>I've tried several methods, involving either creating one 512MB disk
>with mdconfig or mdmfs. No matter what options I specify, the mounted
>mfs works fine until I start filling it up more. For instance, I can
>usually copy the entire /usr/src/sys to /mnt and make depend, but a
>while after I make the kernel panics as a result of the ram disk.
>(specifically citing malloc errors, one time it speicifically spat out a
>number in the order of 251XXXXXX and indicated a malloc bucket limit
>exceeded or something like that)
quote from md(4):
malloc Backing store is allocated using malloc(9). Only one malloc-
bucket is used, which means that all md devices with malloc
backing must share the malloc-per-bucket-quota. The exact size
of this quota varies, in particular with the amount of RAM in
the system. The exact value can be determined with vmstat(8).
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30786.1047929196>