On Tue, May 01, 2007 at 04:39:09PM -0400, Rick Macklem wrote: > > > 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. Or something else is leaking. Really, if there was a problem with MALLOC/FREE we'd see it. KrisReceived on Tue May 01 2007 - 20:20:17 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:09 UTC