Well, the first step is figuring out which UMA zones are actually problematic. Isn't it logging which zones aren't empty?
-a On 26 November 2013 20:01, Craig Rodrigues <rodr...@freebsd.org> wrote: > Adrian, > > As part of looking at this bug in FreeNAS: > > "Panic on new jail with vnet" > https://bugs.freenas.org/issues/3102 > > I started looking at this thread: > > http://lists.freebsd.org/pipermail/freebsd-current/2010-November/021280.html > > Based on this clue from Thiery: > > http://lists.freebsd.org/pipermail/freebsd-current/2010-November/021291.html > > I fixed some VIMAGE related memory leaks related to routetbl. > I also fixed some VIMAGE related kernel panics when > I tried creating and deleting lots of jails: > > http://lists.freebsd.org/pipermail/svn-src-all/2013-November/077178.html > http://lists.freebsd.org/pipermail/svn-src-all/2013-November/077192.html > http://lists.freebsd.org/pipermail/svn-src-all/2013-November/077195.html > > I haven't eliminated all the "Freed UMA keg was not empty" > error messages. > > Do you have any recommendations for how I can track down the last > few UMA related memory leaks? I am new to debugging UMA so > would appreciate any pointers that you may have. > -- > Craig _______________________________________________ email@example.com mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"