Date: Tue, 06 May 2003 06:08:53 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: hschaefer@fto.de Cc: current@freebsd.org Subject: Re: Precaution! Message-ID: <20030506.060853.99162705.imp@bsdimp.com> In-Reply-To: <20030506131623.X65698@daneel.foundation.hs> References: <20030505.112625.16415226.imp@bsdimp.com> <20030506131623.X65698@daneel.foundation.hs>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030506.060853.99162705.imp>