From owner-freebsd-hackers Sun Feb 21 9:17:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BF31F114C3 for ; Sun, 21 Feb 1999 09:17:28 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id JAA02713; Sun, 21 Feb 1999 09:17:12 -0800 Date: Sun, 21 Feb 1999 09:17:12 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Doug Rabson Cc: freebsd-hackers@freebsd.org Subject: Re: Panic in FFS/4.0 as of yesterday - update In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to say that during testing last night (in the middle of which a buildworld got started) the system paniced again with a 'panic: getnewbuf infinite recursion failure'. I've left it in the debugger if anyone could suggest looking at something. I'm going to New Orleans tomorrow so it can sit in the debugger until Friday... A very cursory look at the code makes me wonder 'why the value of 5 for a limit'? It doesn't seem to me a panic is a good solution. On Sat, 20 Feb 1999, Doug Rabson wrote: > On Sat, 20 Feb 1999, Matthew Jacob wrote: > > > > > As of the last set of fixes that added some more splbio protection, the > > testing has gone a lot better. Many thanks. Now I'll start raising the bar > > from 9GB filesystems to > 100GB filesystems with larger blocksizes (unless > > someone says "No! No! Don't do that!") > > Its good that your panic seems to have been addressed but I can't see any > quick solutions for the responsiveness problem. It appears to be a > combination of the way that BSD looks up pathnames and the lack of any > mechanism from stopping writer processes from monopolising the i/o queues. > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message