From owner-freebsd-fs@FreeBSD.ORG Tue Jul 5 20:56:03 2005 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2401C16A41C for ; Tue, 5 Jul 2005 20:56:03 +0000 (GMT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E07C743D4C for ; Tue, 5 Jul 2005 20:56:02 +0000 (GMT) (envelope-from cdillon@wolves.k12.mo.us) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id 315E11FE0A; Tue, 5 Jul 2005 15:56:02 -0500 (CDT) Received: from mail.wolves.k12.mo.us ([127.0.0.1]) by localhost (mail.wolves.k12.mo.us [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 89016-02-2; Tue, 5 Jul 2005 15:55:59 -0500 (CDT) Received: by mail.wolves.k12.mo.us (Postfix, from userid 1001) id D0BA21FE03; Tue, 5 Jul 2005 15:55:59 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by mail.wolves.k12.mo.us (Postfix) with ESMTP id CF6D71A902; Tue, 5 Jul 2005 15:55:59 -0500 (CDT) Date: Tue, 5 Jul 2005 15:55:59 -0500 (CDT) From: Chris Dillon To: Skylar Thompson In-Reply-To: <20050705175559.GA70037@quark.cs.earlham.edu> Message-ID: <20050705155011.F87747@duey.wolves.k12.mo.us> 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> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at wolves.k12.mo.us Cc: fs@freebsd.org Subject: Re: Snapshot problems X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jul 2005 20:56:03 -0000 On Tue, 5 Jul 2005, Skylar Thompson wrote: > On Sun, Jul 03, 2005 at 12:52:01PM +0200, Dag-Erling Smrgrav wrote: >> Skylar Thompson 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?