From owner-freebsd-current@FreeBSD.ORG  Tue May  6 05:11:27 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CEDA637B401
	for <current@freebsd.org>; Tue,  6 May 2003 05:11:27 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1F2F943FB1
	for <current@freebsd.org>; Tue,  6 May 2003 05:11:27 -0700 (PDT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.8/8.12.3) with ESMTP id h46CBQA7052764;
	Tue, 6 May 2003 06:11:26 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Tue, 06 May 2003 06:08:53 -0600 (MDT)
Message-Id: <20030506.060853.99162705.imp@bsdimp.com>
To: hschaefer@fto.de
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030506131623.X65698@daneel.foundation.hs>
References: <20030505.112625.16415226.imp@bsdimp.com>
	<20030506131623.X65698@daneel.foundation.hs>
X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: Precaution!
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 06 May 2003 12:11:28 -0000

In message: <20030506131623.X65698@daneel.foundation.hs>
            Heiko Schaefer <hschaefer@fto.de> writes:
: Hello Warner,
: 
: > If you booted a kernel from approximately April 15th through May 3th,
: > there were a number of small, but critical, vm bugs.  This can cause
: > file system corruption, and leave silent landmines for later.  It is
: > recommended that if you did boot these kernels, you build a newer
: > kernel, come up in single user and force an fsck on all filesystems.
: > This is to prevent 'false' panics later that are a result of the
: > corruption that might be dormant in them now.
: 
: could this bug have caused corruption of the content of files as well ?
: 
: i am having relatively rare cases of corrupted (32kb sized blocks of) data
: which i copy from disk to disk - and am now wondering if this might be
: related.

I don't know.  I think it might, since I've seen one file on my system
become corrupt in the manner that you suggest.

Warner