Corrupted repository... help?

[Niko Matsakis]

Hello,

After upgrading to Mac OS 10.5, I started encountering errors in my  
mercurial repositories.  I am using Mercurial version 0.9.4; I see now  
that there is a more recent release available.  I am not sure if this  
is related to the upgrade or not, but here is an example of the kind  
of message I get:

> $ hg status
> abort: data/Misc.vpdoc/store.vpsqlite.i: no node  
> f6bd5f13be26f08a5e183b958f14b73b241638b2!

after doing some web searching, I found a suggestion to run "hg verify":

> $ hg verify
> checking changesets
> checking manifests
> crosschecking files in changesets and manifests
> checking files
> node f6bd5f13be26f08a5e183b958f14b73b241638b2 in manifests not in  
> Misc.vpdoc/store.vpsqlite
> node 8d1fdeda769d5dfad15946d06bc9351960292245 in manifests not in  
> datapower/hours.numbers/QuickLook/Thumbnail.jpg
> node 419ada638c5800211e662b7352bcb7e2ca348018 in manifests not in  
> datapower/hours.numbers/index.xml.gz
> 25015 files, 370 changesets, 33265 total revisions
> 3 integrity errors encountered!

Unfortunately, I don't see many suggestions about (a) how to repair  
such an error or (b) what might have caused the errors.

One option I could try, I know, is an "hg rollback", but I am afraid  
of losing changes of some sort.  Luckily, in this case, I am the only  
person who works on this repository so I am sure that my file system  
reflects the correct current state.  So, perhaps there is no danger  
from doing an "hg rollback," so long as that command does not affect  
the file system.

The other thing I'd like to know is whether upgrading to 0.9.5 might  
prevent errors like this in the future?


thanks in advance for any help,
Niko Matsakis