From owner-freebsd-stable@FreeBSD.ORG Sun Feb 10 02:41:39 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 68E01BDE for ; Sun, 10 Feb 2013 02:41:39 +0000 (UTC) (envelope-from wollman@hergotha.csail.mit.edu) Received: from hergotha.csail.mit.edu (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2]) by mx1.freebsd.org (Postfix) with ESMTP id 003C03A5 for ; Sun, 10 Feb 2013 02:41:38 +0000 (UTC) Received: from hergotha.csail.mit.edu (localhost [127.0.0.1]) by hergotha.csail.mit.edu (8.14.5/8.14.5) with ESMTP id r1A2fb9F053132 for ; Sat, 9 Feb 2013 21:41:37 -0500 (EST) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.5/8.14.4/Submit) id r1A2fb6t053129; Sat, 9 Feb 2013 21:41:37 -0500 (EST) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20759.2273.284868.12857@hergotha.csail.mit.edu> Date: Sat, 9 Feb 2013 21:41:37 -0500 From: Garrett Wollman To: freebsd-stable@freebsd.org Subject: Interpreting "vmstat -z" output X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (hergotha.csail.mit.edu [127.0.0.1]); Sat, 09 Feb 2013 21:41:37 -0500 (EST) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on hergotha.csail.mit.edu X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2013 02:41:39 -0000 On a server that's been experiencing some issues, I note the following in "vmstat -z": ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 208, 0, 188, 16, 188, 0, 0 UMA Zones: 3456, 0, 188, 0, 188, 0, 0 UMA Slabs: 568, 0, 1209668, 6211,50929964, 0, 0 UMA RCntSlabs: 568, 0, 50791, 1, 50791, 0, 0 UMA Hash: 256, 0, 78, 12, 80, 0, 0 16 Bucket: 152, 0, 227, 23, 227, 0, 0 32 Bucket: 280, 0, 522, 10, 522, 0, 0 64 Bucket: 536, 0, 783, 1, 783, 156, 0 128 Bucket: 1048, 0, 33513, 0, 33513,134423, 0 [...] How should I interpret the failure count for "64 Bucket" and "128 Bucket"? Does it represent a problem, or something that needs to be tuned? There are no obvious tunables, but the code is not exactly transparent. No other zones show failures. -GAWollman