I did restore the entire backup from dump. Took about 1/2 day —luckily I had
a mostly complete dump from some earlier work I had been doing.
The problem turned out to be my fault -- I inadvertently committed a
revision into the backup repository while testing some tools!
P.S: The filthy trick you suggested may work — I think you also have to get
rid of the db/revprops/84333.
On 2/25/08 12:39 AM, "Jonathan Ashley" <jonathan.ashley_at_praxis-his.com>
> If you're using FSFS, you could try this filthy trick on your backup repo:
> (At your own risk...)
> - delete the file db/revs/84333
> - edit the file db/current and change the 84333 to 84332
> - change the revision 0 revprop 'svn:sync-last-merged-rev' to 84332
> - cross your fingers, and run svnadmin verify over the recovered repository.
> I'd probably still do a recovery from backups - wouldn't feel comfortable with
> a repository that had been hand-hacked like this - but it might keep you
> going with a workable live backup in the interim. Restoring an 84000 revision
> repository isn't a trivial task.
> Incidentally, how did this happen? You aren't running svnsync from a
> post-commit hook by any chance?
> Jon Ashley
> From: Murli Varadachari [mailto:mvaradachari_at_facebook.com]
> Sent: 22 February 2008 18:00
> To: Paul Koning
> Cc: users_at_subversion.tigris.org; Internal Use
> Subject: Re: Backup repository corrupted
> Thanks Paul — I was hoping there would be some other faster option but
> (sigh!) I guess in my case (3) is probably the best option.
> There may be another issue though — the rev# 0 properties on the
> restored backup would still indicate that last merged version as being 84333 [
> even if I dumped and restored up to 84332 ]. Does this have to be fixed
> manually too?
> On 2/22/08 9:40 AM, "Paul Koning" <Paul_Koning_at_Dell.com> wrote:
>>>>>> >>>>> "Murli" == Murli Varadachari
>>>>>> <mvaradachari_at_facebook.com> writes:
> Murli> I am doing a backup of my production svn repository
> Murli> svnsync ‹ somehow last night a new version got
> committed to
> Murli> the backup repository directly. AT this point all
> Murli> operations fail.
> Murli> Here is the error message
> Murli> [root_at_svn001.sf2p ~]# svnsync synchronize --username
> Murli> --password root svn://xxxx.foo.com/svnroot svnsync:
> Murli> Destination HEAD (84333) is not the last merged
> Murli> (84332); have you committed to the destination without
> Murli> svnsync?
> Murli> Is there a quick way to fix this.
> I'm not sure about "quick"...
> Some possible approaches:
> 1. Rename the destination repository, create a new one,
> re-sync from
> 2. Restore from a backup of the destination directory, one
> doesn't include the bad rev, and re-sync to that.
> 3. Use svndump to dump up to but not including the bad rev,
> that into a new repository, that's your "repaired"
> This email is confidential and intended solely for the use of the individual
> to whom it is addressed. If you are not the intended recipient, be advised
> that you have received this email in error and that any use, disclosure,
> copying or distribution or any action taken or omitted to be taken in reliance
> on it is strictly prohibited. If you have received this email in error please
> contact the sender. Any views or opinions presented in this email are solely
> those of the author and do not necessarily represent those of Praxis.
> Although this email and any attachments are believed to be free of any virus
> or other defect, no responsibility is accepted by Praxis or any of its
> associated companies for any loss or damage arising in any way from the
> receipt or use thereof. The IT Department at Praxis can be contacted at
> Praxis High Integrity Systems Ltd:
> Company Number: 3302507, registered in England and Wales
> Registered Address: 20 Manvers Street, Bath. BA1 1PX
> VAT Registered in Great Britain: 682635707
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-25 09:52:44 CET