Date: Thu, 3 Jul 2003 09:11:21 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: current@freebsd.org Cc: Cy.Schubert@komquats.com Subject: Re: Corroupted CVS File (fwd) Message-ID: <200307031611.h63GBLRf009280@strings.polstra.com> In-Reply-To: <200307031602.h63G20HN071272@cwsys.cwsent.com> References: <200307031602.h63G20HN071272@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <200307031602.h63G20HN071272@cwsys.cwsent.com>,
Cy Schubert <Cy.Schubert@komquats.com> wrote:
> It appears I may not be going insane after all.
I never suspected you of insanity. :-)
> The file is received OK from cvsup7 and from cvsup10. When I check
> out (using cvs co) from my local repo or rsync the repo to another
> machine on my network here at home, the file is corrupted. Looks
> like I've found some kind of issue with -CURRENT. I'm running
> 5.1-REL.
Next time you find a corrupted RCS file, save it somewhere. Take a
look at it in an editor and see if you can spot what's going on. The
typical kinds of corruption I've seen over the years when people have
reported these things to me have been:
- Single-bit errors in the RCS file. These are always caused by
HW problems, and they always go away if ECC RAM is installed.
- Either a region of zeroes or a portion of an unrelated file
splatted somewhere into the middle of the corrupted RCS file.
This kind of corruption is always page-aligned or filesystem
block aligned. It is probably caused by kernel software bugs.
I used to see a lot of these back around FreeBSD-3.x, but I
haven't heard of any for a long time now.
John
--
John Polstra
John D. Polstra & Co., Inc. Seattle, Washington USA
"Two buttocks cannot avoid friction." -- Malawi saying
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200307031611.h63GBLRf009280>