From owner-freebsd-current@FreeBSD.ORG Mon May 5 10:28:34 2003 Return-Path: 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 4EF7F37B401 for ; Mon, 5 May 2003 10:28:34 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8122543F93 for ; Mon, 5 May 2003 10:28:33 -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 h45HSWA7045127 for ; Mon, 5 May 2003 11:28:32 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 05 May 2003 11:26:25 -0600 (MDT) Message-Id: <20030505.112625.16415226.imp@bsdimp.com> To: current@freebsd.org From: "M. Warner Losh" 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 Subject: Precaution! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 17:28:34 -0000 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. Warner