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

[Scott Timothy E]

I'm running into a problem using largefiles.  My google-fu has failed me, so I'm seeing if someone on this list might be able to lend some insight.

We've got a repo that has been using largefiles successfully for quite some time now.  Today, someone pushed something that broke things.  Here's the error we are seeing when trying to update to the revision with the problem:

% hg update --repository C:\projects\GSX\fpga\jbtest2 --config ui.merge=internal:fail --rev 208 --clean
380 files updated, 0 files merged, 178 files removed, 0 files unresolved
getting changed largefiles
abort: remotestore: largefile 2666200625286a694888ec6cd571fc779ebc7bd5 is invalid
[command returned code 255 Tue Dec 18 09:47:40 2012]
jbtest2%

If I manually copy the largefile in question from the main repo on the server to my local largefiles store, I can update successfully and things work fine.  So, I do not believe that the file itself is bad.  Does anyone know why the file may be detected as "invalid"?

The server machine is running WinXP.  My local machine is running Win7.  I'm using TortoiseHg 2.2.2 / Hg 2.0.2.  The person that apparently introduced the problem is running TortoiseHg 2.2.1 / Hg 2.0.1.

Thanks,
--tim

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121218/f50e5f9d/attachment-0002.html>