From owner-freebsd-current Mon Mar 16 23:57:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26894 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:57:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sos.freebsd.dk (sos.freebsd.dk [195.8.129.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26837; Mon, 16 Mar 1998 23:57:00 -0800 (PST) (envelope-from sos@sos.freebsd.dk) Received: (from sos@localhost) by sos.freebsd.dk (8.8.8/8.8.8) id IAA00561; Tue, 17 Mar 1998 08:56:46 +0100 (MET) (envelope-from sos) Message-Id: <199803170756.IAA00561@sos.freebsd.dk> Subject: Re: Disk munging problem with current solved In-Reply-To: <199803170703.CAA08868@dyson.iquest.net> from "John S. Dyson" at "Mar 17, 98 02:03:44 am" To: dyson@FreeBSD.ORG Date: Tue, 17 Mar 1998 08:56:46 +0100 (MET) Cc: current@FreeBSD.ORG From: Søren Schmidt Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In reply to John S. Dyson who wrote: > I haven't read any emails or complaints yet about filesystem problems, > but I know that those who have tried to run -current in the last day or > so have had terrible problems. The problems didn't manifest for me until > too late, and I ended up with hosed filesystems. The problems were caused > by vtruncbuf doing bad things, and I have corrected them as quickly as > possible. My machine has been down due to the creeping crud associated > with the flaw in the routine. > > Things are looking much better now (for me at least), and I have committed > the fix. Thankyou!!, I was THIS close to trashing my main machine yesterday.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message