From owner-freebsd-current Tue Mar 17 01:00:03 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
by hub.freebsd.org (8.8.8/8.8.8) id BAA03911
for freebsd-current-outgoing; Tue, 17 Mar 1998 01:00:03 -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 AAA03844;
Tue, 17 Mar 1998 00:59:53 -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 CAA05027; Tue, 17 Mar 1998 02:59:53 -0600 (CST)
Received: (from karl@localhost) by Mars.mcs.net (8.8.7/8.8.2) id CAA20237; Tue, 17 Mar 1998 02:59:53 -0600 (CST)
Message-ID: <19980317025953.36408@mcs.net>
Date: Tue, 17 Mar 1998 02:59:53 -0600
From: Karl Denninger <karl@mcs.net>
To: sos@FreeBSD.ORG
Cc: dyson@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Disk munging problem with current solved
References: <199803170703.CAA08868@dyson.iquest.net> <199803170756.IAA00561@sos.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.84
In-Reply-To: =?iso-8859-1?Q?=3C199803170756=2EIAA00561=40sos=2Efreebsd=2Edk=3E=3B_fro?=
=?iso-8859-1?Q?m_S=F8ren_Schmidt_on_Tue=2C_Mar_17=2C_1998_at_08=3A56=3A4?=
=?iso-8859-1?Q?6AM_+0100?=
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG
On Tue, Mar 17, 1998 at 08:56:46AM +0100, Søren Schmidt wrote:
> 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
I just got another case of the same problem with a kernel that has the
believed fix in it, writing to a new filesystem.
BE CAREFUL OUT THERE at the present time.
--
--
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