From owner-freebsd-net@FreeBSD.ORG  Sun Apr 10 21:59:52 2011
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5BF09106564A
	for <freebsd-net@freebsd.org>; Sun, 10 Apr 2011 21:59:52 +0000 (UTC)
	(envelope-from egrosbein@rdtc.ru)
Received: from eg.sd.rdtc.ru (eg.sd.rdtc.ru [62.231.161.221])
	by mx1.freebsd.org (Postfix) with ESMTP id C48148FC12
	for <freebsd-net@freebsd.org>; Sun, 10 Apr 2011 21:59:51 +0000 (UTC)
Received: from eg.sd.rdtc.ru (localhost [127.0.0.1])
	by eg.sd.rdtc.ru (8.14.4/8.14.4) with ESMTP id p3ALxksE050947;
	Mon, 11 Apr 2011 04:59:46 +0700 (NOVST)
	(envelope-from egrosbein@rdtc.ru)
Message-ID: <4DA2284D.2060804@rdtc.ru>
Date: Mon, 11 Apr 2011 04:59:41 +0700
From: Eugene Grosbein <egrosbein@rdtc.ru>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; ru-RU;
	rv:1.9.2.13) Gecko/20110112 Thunderbird/3.1.7
MIME-Version: 1.0
To: Przemyslaw Frasunek <przemyslaw@frasunek.com>
References: <4D947756.6050808@freebsd.lublin.pl>	<4D9F6C71.1040209@frasunek.com>
	<4DA171BA.9000507@frasunek.com> <4DA1E39C.9090300@rdtc.ru>
	<4DA216D8.9090009@frasunek.com>
In-Reply-To: <4DA216D8.9090009@frasunek.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: freebsd-net@freebsd.org
Subject: Re: mpd5/Netgraph issues after upgrading to 7.4
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Apr 2011 21:59:52 -0000

On 11.04.2011 03:45, Przemyslaw Frasunek wrote:
>> Use command "vmstat -z|egrep 'ITEM|NetGraph'" and check FAILURES column.
>> If you see non-zero values there, you need to increase netgraph memory limits
>> net.graph.maxdata and net.graph.maxalloc using /boot/loader.conf.
> 
> Thanks, indeed it helped a lot. I also noticed that other zones have
> non-zero failure counters:
> 
> UMA Slabs:                 64,        0,     2666,     1051,   128676,
>     127
> 128 Bucket:               524,        0,     1455,      316,    82489,
> 97401821
> g_bio:                    132,        0,        0,     3190, 11471737,
>       3
> ata_request:              192,        0,        0,     1880,  2905852,
>     378
> rtentry:                  124,        0,     2513,     1765,   802803,
>     132
> pffrent:                   16,     5075,      175,     3073, 48983719,
>       6
> pffrag:                    48,        0,       39,     3081, 15699916,
>     216
> 
> I'm quite anxious about "ata_request" failures.

In general, you should not worry about failures here - they are transient and normal.

Afaik, that's only mpd that cannot gracefully recover from such errors (it should).
So, increasing mentioned tunnables is only workaround from mpd's deficiency.

Eugene Grosbein