On 3/15/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
>
> On 3/15/07, Tony Thompson <Tony.Thompson@stone-ware.com> wrote:
>
> > It does tell me what the last revision number was that it dumped but,
> > there is lots of stuff in the repository after that revision that I don't
> > want to lose.
> >
>
> I have never had to recover a problem like this. If you can dump up to
> the problem, then skip that revision and dump what comes after, you might be
> able to fix the problem. Just load the first dump file. Do some random
> commit to use up the next revision number, and then load the second dump
> file. The random commit is not strictly necessary if you do not care about
> the revision numbers changing.
>
> Mark
>
>
> It appears that there are other revisions after my corrupt revision that
> also have that same issue. It would be nice if there was a repair option
> that could just fix it for me :) ... but that would be too easy. I can
> dump pieces of the repo so I will work on piecing it back together from that
> unless someone else has any better suggestions.
>
Would you be willing to make the repository available for some post-mortem?
The upside for you is that perhaps a developer could fix it by hand. The
upside for us would be fixing a potential problem.
Is this fsfs or bdb? Have you done anything to muck with any of the files
in the repository directly?
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
Received on Thu Mar 15 20:22:20 2007