Corrupted repository... help?

[Matt Mackall]

On Sun, Nov 04, 2007 at 10:26:31AM +0100, Niko Matsakis wrote:
> 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!

Please run verify with hg 0.9.5. It gives better output, including the
last intact changeset.

Are you using mq? Have you had any notable crashes, power failures, etc?

> One option I could try, I know, is an "hg rollback", but I am afraid  
> of losing changes of some sort.

Well it's always safe to do a rollback on a copy of the repository.

-- 
Mathematics is the supreme nostalgia of our time.