From owner-freebsd-current@FreeBSD.ORG Thu Jul 3 09:11:24 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 1680237B401 for ; Thu, 3 Jul 2003 09:11:24 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF89543FE5 for ; Thu, 3 Jul 2003 09:11:22 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.12.3p2/8.12.3) with ESMTP id h63GBLkF061017 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 3 Jul 2003 09:11:21 -0700 (PDT) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.12.6/8.12.6/Submit) id h63GBLRf009280; Thu, 3 Jul 2003 09:11:21 -0700 (PDT) (envelope-from jdp) Date: Thu, 3 Jul 2003 09:11:21 -0700 (PDT) Message-Id: <200307031611.h63GBLRf009280@strings.polstra.com> To: current@freebsd.org From: John Polstra In-Reply-To: <200307031602.h63G20HN071272@cwsys.cwsent.com> References: <200307031602.h63G20HN071272@cwsys.cwsent.com> Organization: Polstra & Co., Seattle, WA X-Bogosity: No, tests=bogofilter, spamicity=0.500000, version=0.11.2 cc: Cy.Schubert@komquats.com Subject: Re: Corroupted CVS File (fwd) 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: Thu, 03 Jul 2003 16:11:24 -0000 In article <200307031602.h63G20HN071272@cwsys.cwsent.com>, Cy Schubert 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