From owner-freebsd-current Fri Mar 20 09:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA10321 for freebsd-current-outgoing; Fri, 20 Mar 1998 09:44:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA10300 for ; Fri, 20 Mar 1998 09:44:17 -0800 (PST) (envelope-from karl@Mars.mcs.net) Received: from Mars.mcs.net (karl@Mars.mcs.net [192.160.127.85]) by Kitten.mcs.com (8.8.7/8.8.2) with ESMTP id LAA03666; Fri, 20 Mar 1998 11:44:12 -0600 (CST) Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id LAA04153; Fri, 20 Mar 1998 11:44:12 -0600 (CST) Message-ID: <19980320114412.42502@mcs.net> Date: Fri, 20 Mar 1998 11:44:12 -0600 From: Karl Denninger To: Open Systems Networking Cc: current@FreeBSD.ORG Subject: Re: Current status? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84 In-Reply-To: ; from Open Systems Networking on Fri, Mar 20, 1998 at 11:47:33AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Mar 20, 1998 at 11:47:33AM -0500, Open Systems Networking wrote: > > Is current still trashed? I saw johns last commit about an embarrasing > bug, and thought that might be the fix to the invisible run current and > nuke your FS problem. But nothing has been said about that fix, or if > current is still hosed. I don't want to start up another flood of "current > is trashed / mine is running fine" posts, but a simple {yes|no} to wether > the FS problem is fixed yet is all im looking for. And to throw out a > thanks to Karl for finding this hooha of a bug and being VOCAL about it > and what it is doing to your current machine, and john for being the slave > to the VM system he is :) and doing his best to fix the bug. Thanks to > both of you. > > Chris I have completed my first-level regression testing, and it look ok now. MAKE CERTAIN you have the commits from last night however - they were the ones which make it appear, at least, to be "ok". I'm not 100% solid on this yet, and was intending to wait until the weekend was over to say "yes, its ok now" for certain. My confidence level in -CURRENT right now, at least as far as the problem with destroying filesystems goes, is about 90%. However, note that I got a distinctly evil hard lockup with it a while back (ie: no DDB trap possible, etc). No idea what caused it yet, but I'm trying to reproduce that now. -- -- Karl Denninger (karl@MCS.Net)| MCSNet - Serving Chicagoland and Wisconsin http://www.mcs.net/ | T1's from $600 monthly / All Lines K56Flex/DOV | NEW! Corporate ISDN Prices dropped by up to 50%! Voice: [+1 312 803-MCS1 x219]| EXCLUSIVE NEW FEATURE ON ALL PERSONAL ACCOUNTS Fax: [+1 312 803-4929] | *SPAMBLOCK* Technology now included at no cost To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message