From owner-freebsd-current@FreeBSD.ORG Tue May 6 04:18:59 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 0A45E37B401 for ; Tue, 6 May 2003 04:18:59 -0700 (PDT) Received: from sauron.fto.de (p15106025.pureserver.info [217.160.140.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA2C043FBD for ; Tue, 6 May 2003 04:18:57 -0700 (PDT) (envelope-from hschaefer@fto.de) Received: from localhost (localhost.fto.de [127.0.0.1]) by sauron.fto.de (Postfix) with ESMTP id 8895625C101; Tue, 6 May 2003 13:18:55 +0200 (CEST) Received: from sauron.fto.de ([127.0.0.1]) by localhost (sauron [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12787-01; Tue, 6 May 2003 13:18:54 +0200 (CEST) Received: from giskard.foundation.hs (p5091AF60.dip.t-dialin.net [80.145.175.96]) by sauron.fto.de (Postfix) with ESMTP id B70E025C0FE; Tue, 6 May 2003 13:18:53 +0200 (CEST) Received: from daneel.foundation.hs (daneel.foundation.hs [192.168.20.2]) by giskard.foundation.hs (8.9.3/8.9.3) with ESMTP id NAA41296; Tue, 6 May 2003 13:18:46 +0200 (CEST) (envelope-from hschaefer@fto.de) Date: Tue, 6 May 2003 13:18:46 +0200 (CEST) From: Heiko Schaefer X-X-Sender: heiko@daneel.foundation.hs To: "M. Warner Losh" In-Reply-To: <20030505.112625.16415226.imp@bsdimp.com> Message-ID: <20030506131623.X65698@daneel.foundation.hs> References: <20030505.112625.16415226.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at fto.de 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 May 2003 11:18:59 -0000 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. thanks, Heiko