From owner-freebsd-hackers Fri Feb 19 11:35:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 22A9111B85 for ; Fri, 19 Feb 1999 11:35:32 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.2/8.8.8) with ESMTP id TAA81703; Fri, 19 Feb 1999 19:32:00 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 19 Feb 1999 19:32:00 +0000 (GMT) From: Doug Rabson To: Matthew Jacob Cc: freebsd-hackers@freebsd.org Subject: Re: Panic in FFS/4.0 as of yesterday 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 On Thu, 18 Feb 1999, Matthew Jacob wrote: > > Oh, btw- I should clarify a little about this test and some spice to the > mix... The same test on a system that is 25% of the cpu power and 25% of > the memory running solaris 2.7 Intel not only successfully has always runs > this test but also retains a quite acceptable responsiveness. Please don't > make me claim Slowlaris is better! I haven't managed to make my machine crash yet (probably because I have a smaller drive and less memory) but I can certainly reproduce the reponsiveness problem (which is severe). It appears to be caused by a lock cascade leading to the root vnode being locked for long periods of time. I'm not quite sure of the sequence of events yet but it seems that the process holding the vnode lock is being starved out in favour of some of the processes which are writing their huge files. -- 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