Date: Tue, 5 Jul 2005 15:55:59 -0500 (CDT) From: Chris Dillon <cdillon@wolves.k12.mo.us> To: Skylar Thompson <skylar@cs.earlham.edu> Cc: fs@freebsd.org Subject: Re: Snapshot problems Message-ID: <20050705155011.F87747@duey.wolves.k12.mo.us> In-Reply-To: <20050705175559.GA70037@quark.cs.earlham.edu> References: <20050626182031.GA5268@quark.cs.earlham.edu> <20050701130315.C52686@duey.wolves.k12.mo.us> <42C6C873.8050808@cs.earlham.edu> <86k6k8yxf2.fsf@xps.des.no> <20050705175559.GA70037@quark.cs.earlham.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 5 Jul 2005, Skylar Thompson wrote: > On Sun, Jul 03, 2005 at 12:52:01PM +0200, Dag-Erling Smrgrav wrote: >> Skylar Thompson <skylar@cs.earlham.edu> writes: >>> No joy. The machine hung again yesterday afternoon, with the error >>> "kern.ipc.maxpipekva exceeded" repeated over and over again on the >>> console. >> >> So you're using a lot of pipes - more than the kernel can handle >> with the default parameters. What's your workload? Do you run a >> lot of jails? What is the current value of kern.ipc.maxpipekva? >> Have you tried increasing it? > > I doubled it from 16 million to 32 million, and the machine still > crashes. Could this just be a side-effect of the filesystem livelocking (I guess that is the appropriate term) and a script or other process getting out of control as a result? If so, the "kern.ipc.maxpipekva" error would be irrelevant. I don't recall seeing that error when the filesystem livelock happens to me, but I've only actually seen the console a few times when it happened, the rest of the times I had to power-cycle it remotely. -- Chris Dillon - cdillon(at)wolves.k12.mo.us FreeBSD: The fastest, most open, and most stable OS on the planet - Available for IA32, IA64, AMD64, PC98, Alpha, and UltraSPARC architectures - PowerPC, ARM, MIPS, and S/390 under development - http://www.freebsd.org Q: Because it reverses the logical flow of conversation. A: Why is putting a reply at the top of the message frowned upon?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050705155011.F87747>