From owner-freebsd-hackers Thu Feb 25 3:52:26 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 F405214D5D for ; Thu, 25 Feb 1999 03:52:24 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id DAA03926; Thu, 25 Feb 1999 03:52:06 -0800 (PST) (envelope-from dillon) Date: Thu, 25 Feb 1999 03:52:06 -0800 (PST) From: Matthew Dillon Message-Id: <199902251152.DAA03926@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Panic in FFS/4.0 as of yesterday - update References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : :Yow! Indeed that would bung things up. I like also what you said about :getnewbuf shouldn't be converting to async writes. Sounds like real :good progress is happening here. I'll be back tonight and as sooon as :folks are happy with some patches, I'll throw somwe big iron on the :testing. I'll have a tentitive patch tomorrow. I've got all the code in, including fixing the numfreebuffers/numdirtybuffers counters, but it's pretty involved ( not complex, but lots of little changes in kern/vfs_bio.c and nfs/nfs_vnops.c ) and I gotta get to bed. nfs/nfs_vnops.c is mostly responsible for messing up numfreebuffers but kern/vfs_bio.c also screws it up in certain cases, mainly because people have hacked it over the years and never documented the rules. I think it's going to be a whole lot happier with numfreebuffers fixed *AND* the write recursion removed from getnewbuf(). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message