From owner-freebsd-current@FreeBSD.ORG  Tue Jan 27 11:13:33 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 29F6616A4CE
	for <current@freebsd.org>; Tue, 27 Jan 2004 11:13:33 -0800 (PST)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id 60D1443D48
	for <current@freebsd.org>; Tue, 27 Jan 2004 11:12:59 -0800 (PST)
	(envelope-from silby@silby.com)
Received: (qmail 12246 invoked from network); 27 Jan 2004 19:11:12 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 27 Jan 2004 19:11:12 -0000
X-pair-Authenticated: 209.68.2.70
Date: Tue, 27 Jan 2004 13:11:10 -0600 (CST)
From: Mike Silbersack <silby@silby.com>
To: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= <des@des.no>
In-Reply-To: <xzpptd5mep9.fsf@dwp.des.no>
Message-ID: <20040127130947.C4636@odysseus.silby.com>
References: <20040119233546.S39477@odysseus.silby.com>
	<xzpznc9tzgz.fsf@dwp.des.no><xzpr7xl8i1a.fsf@dwp.des.no>
	<xzpptd5mep9.fsf@dwp.des.no>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-8859-1
Content-Transfer-Encoding: QUOTED-PRINTABLE
X-Mailman-Approved-At: Wed, 28 Jan 2004 06:12:04 -0800
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, 27 Jan 2004 19:13:33 -0000


On Tue, 27 Jan 2004, Dag-Erling [iso-8859-1] Sm=F8rgrav wrote:

> Mike Silbersack <silby@silby.com> writes:
> > There is a limit, no single pipe can grow beyond BIG_PIPE_SIZE, which i=
s
> > presently defined as 64K.  Well, unless there is a leak, of course. :)
>
> 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...

Whoa!

>
> > Is it really crashing?  That's not supposed to happen. :(
>
> Yes, it crashes when it runs out of pipekva.  I wasn't there when it
> happened, but I did get a frantic phone call asking what to do :|

Double whoa.  You'd better see if you can recreate this problem before
investigating any of what I wrote; the code as it exists right now should
have handled that situation without a problem.

Mike "Silby" Silbersack