Broken repo? "abort: remotestore: largefile xxx is invalid"

[Matt Harbison]

On Tue, 18 Dec 2012 13:59:44 -0600, Scott Timothy E wrote:

> (Sorry for the top-post...)
> 
> We settled on option #2.  We went in and got rid of the largefiles that
> introduced the problem.
> 
> Thanks for the help and links to the related issues.
> 
> --tim

You should probably run this to make sure there aren't other damaged 
largefiles in other revisions:

  $ hg verify --large --lfa --lfc --config paths.default=

It will complain about missing files that you haven't downloaded, but 
shouldn't complain about corruption.  The path config makes it look 
locally for the files instead of going to the server.  It's probably also  
worth running on the server, and anywhere else the old repo has been.

Back when I had this problem, I also went into the system cache and 
verified that the checksum of each file matched its name, and got rid of 
the ones that didn't.  I think I used a command in OpenSSL on OSX to print 
the hash of each file, so that's likely an option for the Windows port 
too.  I've seen strange behavior when a corrupt file is in the cache that 
I haven't been able to completely track down yet.

--Matt