ZFS committed to the FreeBSD base.
rmacklem at uoguelph.ca
Tue May 1 20:38:13 UTC 2007
On Tue, 1 May 2007, Kris Kennaway wrote:
>> I don't know if it relevent, but I've seen "kmem_map: too small" panics
>> when testing my NFSv4 server, ever since about FreeBSD5.4. There is no
>> problem running the same server code on FreeBSD4 (which is what I still
>> run in production mode) or OpenBSD3 or 4. If I increase the size of the
>> map, I can delay the panic for up to about two weeks of hard testing,
>> but it never goes away. I don't see any evidence of a memory leak during
>> the several days of testing leading up to the panic. (NFSv4 uses
>> MALLOC/FREE extensively for state related structures.)
> Sounds exactly like a memory leak to me. How did you rule it out?
Well, I had a little program running on the server that grabbed the
mti_stats out of the kernel and logged them. I had one client mounted
running thousands of passes of the Connectathon basic tests (one client,
same activity over and over and over again). For a week, the stats don't
show any increase in allocation for any type (alloc - free doesn't get
unreasonably big), then..."panic: kmem_map too small". How many days it
took to happen would vary with the size of the kernel map, but no evidence
of a leak prior to the crash. It seemed to be based on the number of times
MALLOC and FREE were called.
Also, the same server code (except for the port changes, which have
nothing to do with the state handling where MALLOC/FREE get called a lot),
works fine for months on FreeBSD4 and OpenBSD3.9.
So, I won't say a "memory leak is ruled out", but if there was a leak why
wouldn't it bite FreeBSD4 or show up in mti_stats?
I first saw it on FreeBSD6.0, but went back to FreeBSD5.4 and tried the
same test and got the same result.
More information about the freebsd-current