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

[Scott Timothy E]

(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


-----Original Message-----
From: Matt Mackall [mailto:mpm at selenic.com] 
Sent: Tuesday, December 18, 2012 1:33 PM
To: Scott Timothy E
Cc: mercurial at selenic.com
Subject: RE: Broken repo? "abort: remotestore: largefile xxx is invalid"

On Tue, 2012-12-18 at 11:35 -0600, Scott Timothy E wrote:
> FWIW, I updated to the latest version of TortoiseHg / Mercurial and the update log now shows:
> 
> % hg update --repository C:\projects\gsx\fpga\jbtest --config 
> ui.merge=internal:fail --rev 207 --clean
> 102 files updated, 0 files merged, 0 files removed, 0 files unresolved 
> getting changed largefiles
> smartxplorer_results/run1/gsx_server_pb1b.pcf: data corruption 
> (expected 2666200625286a694888ec6cd571fc779ebc7bd5, got 
> a0e83c6556cb68a9ee346d7fa18d602d8ee95b79)
> smartxplorer_results/run2/gsx_server_pb1b.pcf: data corruption 
> (expected c024bcd2a2058369f993e5c291d2ed5c1981112f, got 
> b43fe59586e6dcc4e4351d2428336b8e90f2d22c)

Some possible paths forward:

- replaced the damaged files in the store with files that match the hash
- rebuild your repo, filtering out the damaged changes
- live with it

The first is probably the best, if you can reconstruct the data exactly.
Otherwise, I'd probably go with the last.

--
Mathematics is the supreme nostalgia of our time.