From owner-freebsd-questions@FreeBSD.ORG Sat Oct 22 09:10:01 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27E5B16A41F for ; Sat, 22 Oct 2005 09:10:01 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC61943D4C for ; Sat, 22 Oct 2005 09:10:00 +0000 (GMT) (envelope-from infofarmer@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so355733nzo for ; Sat, 22 Oct 2005 02:10:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=f7tx/xnm5ZyULYFInvPlpIq25c5pqyj4aX6ea4iPIbs3gfMAO36GOEPRxit3Mpaw9uQsagutCZ6JneGaL8BvoZXsm/LEmxPsEVhRejh8PhNIxe0yW6+smf4bBRRdBhf/wah53U3b2ZA3s5navnoaaWwXtYwZr/ls/d0L64omy2Y= Received: by 10.36.146.8 with SMTP id t8mr3762451nzd; Sat, 22 Oct 2005 02:10:00 -0700 (PDT) Received: by 10.37.20.34 with HTTP; Sat, 22 Oct 2005 02:09:59 -0700 (PDT) Message-ID: Date: Sat, 22 Oct 2005 13:09:59 +0400 From: "Andrew P." To: FreeBSD Questions MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: cvsup, mirrors and data integrity X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Oct 2005 09:10:01 -0000 So I have a cvsup mirror, set up with net/cvsup-mirror port. It was ok until the server crashed (all my fault, really) and fsck came up with all that soft-updates related stuff and what not. Anyway, cvsup-mirror seems to not have noticed the crash at all, but some clients cvsupping from this mirror report unexpected syntax errors during buildworld. They cease to do so once cvsupped from another mirror, but only if I remove src completely before it. Cvsupping the broken sources against the good ones doesn't find a mistake at all. My question is: what mechanisms do cvsup and cvsupd have to deal with data corruption? I know about the -s switch, but it doesn't help to disable it in my situation. How do I repair broken sources or repo, using a good cvsup repo. How do I prevent this from happening again without disabling soft- updates? Thanks, Andrew P.