Many missing revlogs, do we have a problem?

[Simon King]

On Thu, Jun 18, 2015 at 8:57 AM, Alban Hertroys
<alban.hertroys at apollovredestein.com> wrote:
> Simon King <simon at simonking.org.uk> wrote on 17/06/2015 18:11:06:
>
>> On Wed, Jun 17, 2015 at 3:58 PM, Alban Hertroys
>> <alban.hertroys at apollovredestein.com> wrote:
>> > I just tried a synchronize with a local copy of our master repo and it
>> > failed with "empty or missing revlog". So I figured there might be a
> few
>> > corrupted revlogs somewhere and did an hg verify on our master repo
> (using
>> > tortoisehg 3.3). I was NOT prepared for what it told me, an excerpt
> from
>> > the end of the (long) list:
>> >
>> > data/xxx_austrian_env/SalesreportPointSAustriaS.fex.i at 1883: missing
>> > revlog!
>> >  data/xxx_austrian_env/SalesreportPointSAustriaS_RC.fex.i at 1883:
> missing
>> > revlog!
>> >  data/xxx_austrian_env/SalesreportPointSAustriaStart.fex.i at 1883:
> missing
>> > revlog!
>> >  data/xxx_austrian_env/points.csv.i at 1883: missing revlog!
>> > 17922 files, 2741 changesets, 26977 total revisions
>> > 13 warnings encountered!
>> > 17985 integrity errors encountered!
>> > (first damaged changeset appears to be 0)
>> >
>> > It's telling me that we have even more integrity errors than we have
>> > files. Ouch!
>> >
>> > Last time I synchronized to my local copy was sometime last week and
> that
>> > went fine. Now suddenly we're in _this_ situation, and of course just
> as
>> > we're about to release the committed code to our new production
> server. I
>> > find it rather hard to believe that hg verify is telling me the truth,
>> > frankly - it doesn't make sense...
>> >
>> > Any idea how this might have happened?
>> > What can we do about it without losing our master repo?
>> >
>>
>> First, take a backup of the master repository, and only work on the
>> backup. Don't touch the master repository until we've got to the
>> bottom of the problem.
>
> That's not as easy as it sounds; that repo is 37GB (including data files
> not under version control) and we only have about 30GB of free space on
> that machine - and less during the night when the disk fills up with
> temporary files.
> Then again, I don't suppose it matters whether we keep working on the
> master repo and investigate on a copy or vice-versa?
>

The most important thing to back up is the .hg directory, which (from
your other message) is relatively small.

>> Does "hg verify" work in your local repository?
>
> It does; just a few warnings (that I probably should fix!).
>
>> In your (backup of the) master repository, do you have a file called
>> .hg/store/data/fncache?
>
> Nope.
>

Sorry, my mistake, I got the path wrong. As you noticed, it should be
.hg/store/fncache

Simon