From owner-freebsd-stable@FreeBSD.ORG Sat May 5 20:11:39 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0AE216A401 for ; Sat, 5 May 2007 20:11:39 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id AA3A113C45A for ; Sat, 5 May 2007 20:11:39 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.8/8.13.7) with ESMTP id l45KBaFM098052; Sat, 5 May 2007 13:11:36 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.13.8/8.13.4/Submit) id l45KBZGk098049; Sat, 5 May 2007 13:11:35 -0700 (PDT) Date: Sat, 5 May 2007 13:11:35 -0700 (PDT) From: Matthew Dillon Message-Id: <200705052011.l45KBZGk098049@apollo.backplane.com> To: "Marc G. Fournier" References: <5BF35D39E7EDDE250B00BA98@ganymede.hub.org> Cc: John-Mark Gurney , freebsd-stable@freebsd.org, corwin@aeternal.net, "Marc G. Fournier" Subject: Re: swap zone exhausted, increase kern.maxswzone X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 May 2007 20:11:39 -0000 :That's why I think that the socket issue and this one are co-related ... with :everything started up (93 jails), my swap usage right now is: : :mars# pstat -s :Device 1K-blocks Used Avail Capacity :/dev/da0s1b 8388608 20 8388588 0% : :Its only been up 2.5 hours so far, but still, everything is started up ... : :- ---- :Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) The "swap zone exhausted, increase kern.maxswzone" message only prints if uma_zone_exhausted() returns TRUE. uma_zone_exhausted() appears to be based on a UMA flag which is only set if the pages for the zone exceeds some maximum setting. Insofar as I can tell, vmstat -z on FreeBSD will dump the UMA zones, so try using that when the problem occurs along with pstat -s. It sounds like there is a leak somewhere (but I don't see how anything in any other UMA zones could cause the SWAPMETA zone to fill up). Or the maximum setting is too low, or something is getting lost somewhere. We'll have a better idea as to what is going on when you get the message again. You might even want to do a once-a-10-minutes cron job to append pstat -s, vmstat -m, and vmstat -z to a file. -Matt Matthew Dillon