panic with heavy writing on md device
ronald-freebsd7 at klop.yi.org
Tue Jun 29 18:11:22 PDT 2004
On Tue, 29 Jun 2004 19:52:21 -0400, Brian Fundakowski Feldman
<green at freebsd.org> wrote:
> On Tue, Jun 29, 2004 at 11:11:51PM +0200, Ronald Klop wrote:
>> I got a panic while doing a lot of IO on a md device.
>> I attached a gdb backtrace of the kernelcore and a dmesg output.
>> It happened while untarring a 30 MB tar on the background (&) and
>> traversing this new directory in the meantime.
>> uname -a
>> FreeBSD guido.thuis.klop.ws 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Fri Jun
>> 04:03:35 CEST 2004
>> root at guido.thuis.klop.ws:/usr/obj/usr/src/sys/GUIDO i386
>> On the same time I was playing music with mpg123, but that doesn't make
>> use of the md device.
>> I have had this more and always while doing a lot of IO on the md
>> Is there more info you need?
> It looks like there is a memory leak -- in general, you are not supposed
> to run out of kernel virtual memory address space unless you have a
> dire misconfiguration somewhere.
> Unfortunately, I think the most useful pieces of information (zone and
> malloc allocation) are not fetchable via kvm anymore. Here's a fix for
> vmstat so that you can provide vmstat -m output using the -M and -N
> args again. I think vmstat -c output would also be useful.
Thanks, I solved it. See my other thread about kmem_malloc.
I thought that was about another error, so I opened a new thread.
Amsterdam, The Netherlands
More information about the freebsd-current