From owner-freebsd-current Mon Mar 16 23:03:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16728 for freebsd-current-outgoing; Mon, 16 Mar 1998 23:03:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16717 for ; Mon, 16 Mar 1998 23:03:46 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id CAA08868 for current@freebsd.org; Tue, 17 Mar 1998 02:03:44 -0500 (EST) (envelope-from toor) Message-Id: <199803170703.CAA08868@dyson.iquest.net> Subject: Disk munging problem with current solved To: current@FreeBSD.ORG Date: Tue, 17 Mar 1998 02:03:44 -0500 (EST) From: "John S. Dyson" Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- John | Never try to teach a pig to sing, dyson@freebsd.org | it just makes you look stupid, jdyson@nc.com | and it irritates the pig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message