On Tue, Sep 28, 2010 at 10:50 PM, Steve Borho <[email protected]> wrote:
> On Wed, Sep 29, 2010 at 12:36 AM, Luis Navarro <[email protected]>
> wrote:
> > I have a TortoiseHG installation that's been running cleanly for a few
> > months. However, in the past week, one of my users has managed to get
> into
> > two situations that have resulted in repository corruption and I can't
> > figure out why.
> >
> > Today's problem arose when the user was pushing changes from our staging
> > repo to our production repo. The production repo is setup with
> changegroup
> > hooks to (a) automatically update the production files and (b) send a
> > notification e-mail (using the "notify" extension).
> >
> > The push generated the following error:
> >
> > pushing to y:\production\
> > searching for changes
> > adding changesets
> > adding manifests
> > adding file changes
> > added 2 changesets with 0 changes to 0 files
> > warning: changegroup hook exited with status -1
> > [command completed successfully Tue Sep 28 16:02:29 2010]
> > error: changegroup.notify hook raised an exception:
> > data/web/shared/pubs/workshops/index.cf...@919619b0c5ef: no match found
>
> 0 changes to 0 files is normal if you are pushing merge changesets
> that did not introduce any new file changes (no files required
> merging)
>
> > The "0 changes to 0 files" part is curious. I'd also love more info on
> the
> > "changegroup hook exited with status -1" part. Is there a way to get THG
> to
> > provide more verbose information, perferably to a file so I don't have to
> > count on my users diligently sending me error info.
>
> The 'changegroup.notify' hook warning is coming from an hook you have
> registered, I guess from the notify extension. My guess is that it is
> a symptom of a larger problem.
>
> > After this error, I ran "verify" on the staging and production repos and
> got
> > the following results:
> >
> > Staging repo:
> >
> > repository uses revlog format 1
> > checking changesets
> > checking manifests
> > crosschecking files in changesets and manifests
> > checking files
> > web/shared/pubs/workshops/index....@?: rev 1 points to unexpected
> changeset
> > 116
> > (expected 117)
> > 1 warnings encountered!
> > 1 integrity errors encountered!
> > 8515 files, 119 changesets, 8669 total revisions
>
> If you can reproduce this problem by replaying the push to the repo
> (clone it to the revision before the push, then push again), then most
> certainly file a bug report for it. But it's much more likely you
> have a disk that's starting to malfunction.
>
> > Production repo:
> >
> > repository uses revlog format 1
> > checking changesets
> > checking manifests
> > crosschecking files in changesets and manifests
> > checking files
> > web/shared/pubs/workshops/index....@117: 919619b0c5ef in manifests not
> > found
> > 1 integrity errors encountered!
> > (first damaged changeset appears to be 117)
> > 8515 files, 119 changesets, 8668 total revisions
> > [command returned code 1 Tue Sep 28 17:30:15 2010]
> >
> > I know how to fix these repos (by cloning them to the changeset before
> the
> > bad one and re-adding/updating the files in the bad changeset) but its a
> bit
> > of a hassle. My bigger question is what's causing this corruption and
> how
> > do I prevent it? I'm really happy with Mercurial and THG so far but am
> > concerned they may be a bit too fragile for my users.
> >
> > Thanks!
> >
> >
> ------------------------------------------------------------------------------
> > Start uncovering the many advantages of virtual appliances
> > and start using them to simplify application deployment and
> > accelerate your shift to cloud computing.
> > http://p.sf.net/sfu/novell-sfdev2dev
> > _______________________________________________
> > Tortoisehg-discuss mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
> >
> >
>
>
>
> --
> Steve Borho
>
I've been trying for the past 2 days but haven't been able to reproduce this
problem. The problem seems to be a combination of changesets 116-118 so I
made clones of staging and production at changeset 115 and used a backup of
the corrupted dev repo (still at 118) and had no problems pushing changesets
116-118 to staging and then from staging to production. I've still got
backups of all 3 repos so I'll (per Martin's suggestion) send something to
the Mercurial list and see if they can provide any debugging help.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
