panic: kmem_malloc; Should I increase some setting?
Robert Watson
rwatson at freebsd.org
Tue Jun 29 18:33:25 PDT 2004
On Tue, 29 Jun 2004, Doug White wrote:
> On Wed, 30 Jun 2004, Ronald Klop wrote:
>
> > I get the following panics while untarring a 30MB archive on an md device
> > create with:
> > tmpmfs="YES"
> > tmpsize="256m"
>
> This is a malloc-backed md disk, which consumes memory directly from
> KVM. If you do a large extraction it will consume all of KVM and cause
> your panic. Unless you're running diskless and this is your only option
> besides NFS, either don't use tmpmfs or avoid extracting large amounts
> of data to /tmp.
What you want to do is use a swap-backed /tmp, assuming there's local
swap. We should probably discuss why the rc.conf bits use malloc-backed
by default in what sounds like a non-diskless environment?
Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
robert at fledge.watson.org Principal Research Scientist, McAfee Research
>
> > panic: kmem_malloc(16384): kmem_map too small: 86233088 total allocated
>
> --
> Doug White | FreeBSD: The Power to Serve
> dwhite at gumbysoft.com | www.FreeBSD.org
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>
More information about the freebsd-current
mailing list