From owner-freebsd-current@FreeBSD.ORG  Tue Feb  3 08:54:56 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7089616A4CF
	for <current@freebsd.org>; Tue,  3 Feb 2004 08:54:56 -0800 (PST)
Received: from plouf.absolight.net (plouf.absolight.net [212.43.217.12])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D509343D1F
	for <current@freebsd.org>; Tue,  3 Feb 2004 08:54:54 -0800 (PST)
	(envelope-from mat@FreeBSD.org)
Received: from localhost (localhost [127.0.0.1])
	by plouf.absolight.net (Postfix) with ESMTP
	id 547394FD3FA; Tue,  3 Feb 2004 17:54:53 +0100 (CET)
Received: from andromede.faubourg.reaumur.net
	(ATuileries-107-2-1-195.w217-128.abo.wanadoo.fr [217.128.120.195])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(Client did not present a certificate)
	by plouf.absolight.net (Postfix) with ESMTP
	id B4BB34FD3BE; Tue,  3 Feb 2004 17:54:51 +0100 (CET)
Date: Tue, 03 Feb 2004 17:54:40 +0100
From: Mathieu Arnold <mat@FreeBSD.org>
To: Mike Silbersack <silby@silby.com>,
	=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no>
Message-ID: <84762968.1075830880@andromede.faubourg.reaumur.net>
In-Reply-To: <20040127130947.C4636@odysseus.silby.com>
References: <20040119233546.S39477@odysseus.silby.com>
	<xzpznc9tzgz.fsf@dwp.des.no><xzpr7xl8i1a.fsf@dwp.des.no>
	<20040127130947.C4636@odysseus.silby.com>
X-Mailer: Mulberry/3.1.1 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-Virus-Scanned: by amavisd 0.1
cc: current@freebsd.org
Subject: Re: 'kern.maxpipekva exceeded' messages...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Feb 2004 16:54:56 -0000

+-le 27/01/2004 13:11 -0600, Mike Silbersack =E9crivait :
|=20
| On Tue, 27 Jan 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote:
|=20
|> Mike Silbersack <silby@silby.com> writes:
|> > There is a limit, no single pipe can grow beyond BIG_PIPE_SIZE, which is
|> > presently defined as 64K.  Well, unless there is a leak, of course. :)
|>=20
|> The backup script uses exactly *one* pipe (between dump and ssh), and
|> that one pipe seems to make all the difference between using barely
|> 300 kB pipe kva, and hitting the 8 MB limit...
|=20
| Whoa!

I've been running into about the same problem for quite some time now, my box
crashes while running some periodic job. Some find never end, they stack up,
and when my coworkers usually do a killall -9 find, the box is unresponsive
from network, and after a reboot, it says 2 or 3 times 'kern.maxpipekva
exceeded...' in syslog.

I'd try to see what makes it block next time it happens.

--=20
Mathieu Arnold