ZFS committed to the FreeBSD base.

Kris Kennaway kris at obsecurity.org
Tue May 1 16:02:14 UTC 2007

On Tue, May 01, 2007 at 10:41:10AM -0400, Rick Macklem wrote:
> On Tue, 1 May 2007, Peter Schuller wrote:
> >>This does seem to eliminate the problem here too.
> >
> >It appears the problem persists, but is more difficult to trigger.
> [stuff snipped]
> >It takes on the order of several hours to trigger it.
> 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?

> So, I'm wondering if maybe there is some subtle bug in MALLOC/FREE (maybe
> i386 specific, since that's what I test on)?

That would be unlikely.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070501/87c7ed6d/attachment.pgp

More information about the freebsd-current mailing list