From owner-freebsd-hackers Thu Feb 25 15: 1:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 680D614E73 for ; Thu, 25 Feb 1999 15:01:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA09541; Thu, 25 Feb 1999 15:00:49 -0800 (PST) (envelope-from dillon) Date: Thu, 25 Feb 1999 15:00:49 -0800 (PST) From: Matthew Dillon Message-Id: <199902252300.PAA09541@apollo.backplane.com> To: Julian Elischer Cc: Luoqi Chen , dfr@nlsystems.com, freebsd-hackers@FreeBSD.ORG, mjacob@feral.com Subject: Re: Panic in FFS/4.0 as of yesterday - update References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : : :On a related note.... :and something PHK has been on about... : :the BUF struct.. (yech) :this is overlayed with two totally separate functions. : :one id to keep track of IO states, :and the other is to track content of the buf and the state of the :contents. Poul has talked of splitting these tow functions and I tend to :agree with him.. I tend to agree. There are actually three things: * logical block translation * I/O in progress * Contents of the buffer But lets fix what we have first before we rip it up. The patch I've supplied has one bug in it that came up... While building the world one of my 'ranlib's got stuck in 'newbuf' even after plenty of buffers were freed up. I think it's a simple missing wakeup... when I spiked the load the ranlib got going again ( too bad, I was trying to gdb -k the running system and the gdb command unstuck the ranlib! ). I should be able to find this bug fairly quickly and supply a new patch. It's the only bug I've found so far. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message