From owner-freebsd-current Mon Oct 18 17:13:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 8A9AC153D3 for ; Mon, 18 Oct 1999 17:13:23 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id RAA78407; Mon, 18 Oct 1999 17:12:41 -0700 (PDT) Date: Mon, 18 Oct 1999 17:12:41 -0700 (PDT) From: David Wolfskill Message-Id: <199910190012.RAA78407@pau-amma.whistle.com> To: brettw@cs.rmit.edu.au, freebsd-current@FreeBSD.ORG Subject: Re: 4.0-19991012-CURRENT In-Reply-To: <19991019095649.A14736@cs.rmit.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 19 Oct 1999 09:56:49 +1000 >From: Brett White >Has anyone tried using the 4.0-19991012-CURRENT snapshot? I >need to confirm that this snapshot is a "good one" before I >update my 3.3R installation to it in a last ditch effort to >compile USB modem support into the kernel. I'm currently using 4.0-19991012-CURRENT and trying -- so far, unsuccessfully -- to break it (as I broke(*) 3.2-R & 3.3-R) with a script that does some fairly aggressive file creation/deletion. I haven't done much more than that with it, though. (Well, I persuaded it to "play nice" in our Engineering net, NIS and all. And it uses amd OK.) (I'm stress-testing the machine because I'm trying to set up a new amanda server, and I want to do a better job of it than I did last time. The script is kinda dumb, but moderately effective, at simulating the kind of load an active amanda server puts on ts "holding disk".) *"Broke" as in panic. Called Julian over to have a look; he suggested trying 3.3-R, then a recent CURRENT snap. Panic, as I recall, was whimpering about an attempt to free a vnode that was already marked free. Hope that's useful, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message