[cvsnt] Odd corruption problem

[Glen Starrett]

I'd start with the latest stable build of CVSNT on the server--your build is
very old, and that is likely at least part of the problem.

AV software "real time scans" lock the file once it is written or modified
typically causing errors something like "can't rename...".  I would imagine
it is possible for the same thing to happen with backups, especially ones
that are relatively slow (network to tape).  In that case I would recommend
using a interim backup method, like I described a couple weeks ago (search
the newsgroup for the subject "repos back up"--I looked it up after the last
person asked).  Once you have that set up, you let the script back up CVS
safely to the same drive, then tell your network backup to skip the CVS
repositories and just grab the script-produced archive(s).

Maybe someone wants to post a wiki document about recommended backup
procedures for CVSNT?  Is there one already?

Hope this helps.

Regards,

Glen Starrett

-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Carl Zmola
Sent: Friday, June 06, 2003 8:16 AM
To: cvsnt at cvsnt.org
Subject: [cvsnt] Odd corruption problem



I've had  problems with locks being left in the repostiory and corruption
of some of my files.  I have noticed that there have been warnings
about using Anti Virus software on the server.  Would similar problems
occur if the disk was being backed up? (tape backup over a network).
What does the Anti Virus software do that causes problems?

The major problem is that I have lost the history on some of my files
(Invalid change text, where there are 3 consecutive intermediate
versions that have said that they have deleted the whole file (the RCS
entry says @d1 106) and of course if you have deleted the whole file
in version 1.15, you can't delete everything again in version 1.14.

In tracking down this issue, any abnormality has been brought to my
attention, including clients that appear to hang.  If the client is killed,
reissuing the command often works.

I may have found the root of the corruption problem in an older (file
date 2001) version of cvs.exe that was installed by WinCVS on one of
the clients.  I don't know why this would matter, other than seeing a
bunch of emails on the list that point in this direction.

I am running an older version of cvsnt 1.11.1.3 (build 57j)  and am in
the process of updating our server and clients to the latest version, but
I am a little concerned about a corrupt repository.

I guess I am looking for a plausable reason the repository was
corrupted, and a some measures I can take to prevent it from
happening again.


----------------------------------------------------------------------------
---------
Carl Zmola
Carl at MembersOnlySoftware.com
202-328-1698
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt