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> Cc: current@freebsd.org Subject: Re: 'kern.maxpipekva exceeded' messages... 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>
next in thread | previous in thread | raw e-mail | index | archive | help
+-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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84762968.1075830880>