Date: Thu, 08 May 1997 22:46:44 -0700 From: John Polstra <jdp@polstra.com> To: freebsd-hackers@freebsd.org Subject: Users of CVSup2.FreeBSD.ORG please read! Message-ID: <199705090546.WAA25238@austin.polstra.com>
next in thread | raw e-mail | index | archive | help
CVSup2.FreeBSD.ORG developed RAM problems beginning May 7, 1997.
The problems have now been fixed, but while they lasted some file
corruption occurred. This took the form of little 1-bit errors
scattered through a number of files, including some served by CVSup.
I have run MD5 checksums on the entire CVS repository both on
freefall and on CVSup2. Here is a list of files which may have
been corrupted:
CVSROOT/commitlogs/gnu
CVSROOT/commitlogs/ports
CVSROOT/commitlogs/share
CVSROOT/commitlogs/sys
CVSROOT/commitlogs/usrsbin
src/gnu/usr.bin/gdb/Attic/ChangeLog,v
src/sys/i386/i386/math_emulate.c,v
src/usr.sbin/ppp/lqr.c,v
I have replaced the possibly-corrupted files with fresh copies from
freefall, but people who did updates from CVSup2 during the past
two days may have gotten bad copies. CVSup checksums all updated
files, but it cannot detect errors that occur in RAM between the
times when the program writes the data and the kernel flushes it
to disk.
If you ran a CVSup update from CVSup2 on May 7 or May 8, please
delete the files listed above from your local repository, and do
another update to replace them with known good versions.
There is some chance that the RAM errors caused some files to go out
corrupted even though the corruption didn't show up on disk.
Unfortunately, there is no way of knowing whether that happened.
The RAM has been replaced and CVSup2 is working fine again now.
--
John Polstra jdp@polstra.com
John D. Polstra & Co., Inc. Seattle, Washington USA
"Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705090546.WAA25238>