Re: CVS corruption or other?

[Sarah Gonzales]

Thx VERY much for the response. One other question and I apologize, 
it's probably fairly basic.

When I run the validate script, there were 2 results.

1. corruption of files in the Attic - should I be concerned with this? 
Is it safe to just remove these files from the file system? I assume 
this will effect my history.

2. There were only a handful of files that actually indicated 
CORRUPTION. The others, in much greater #s indicated that they were 
"extra files" and were listed as

        => List of Files That Don't belong in Repository:

what's the distinction b/t "extra" files and "corrupted" files. The 
latter is obvious, but I'm not sure what the "extra" is all about.

appreciate all the help thus far! I'm so much further along using CVS 
having "lurked" on this mailing list for a while now.


On Oct 27, 2004, at 3:57 PM, Larry Jones wrote:

> Yes, you have a corrupted repository.  Is your repository on an
> NFS-mounted file system?  Nearly every report of repository corruption
> we've ever received has been traced to NFS interoperability bugs.  If
> you do have an NFS-mounted repository, I strongly urge you to move it 
> to
> a local disk as soon as possible before you do any more damage.
>
> There is a perl script in the contrib directory that checks the entire
> repository: it's called validate_repo or check_cvs depending on which
> release of CVS you have.  You should run it to determine the extent of
> the damage.  There is no good way to recover from repository damage.
> The simplest thing to do is restore the damaged files from a good 
> backup
> (if you have one) and then re-do any subsequent changes.  
> Alternatively,
> you might be able to edit the RCS file by hand to repair the damage, 
> but
> that requires a fair amount of knowledge of the RCS file format and is
> not for the faint of heart.
>
> -Larry Jones