RE: Re: Backup repository corrupted
From: Jonathan Ashley <jonathan.ashley_at_praxis-his.com>
Date: Mon, 25 Feb 2008 08:39:09 +0000
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
I'd probably still do a recovery from backups - wouldn't feel comfortable with
Incidentally, how did this happen? You aren't running svnsync from a
regards,
-- 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? murli 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 using Murli> svnsync ‹ somehow last night a new version got committed to Murli> the backup repository directly. AT this point all synsync Murli> operations fail. Murli> Here is the error message Murli> [root_at_svn001.sf2p ~]# svnsync synchronize --username root Murli> --password root svn://xxxx.foo.com/svnroot svnsync: Murli> Destination HEAD (84333) is not the last merged revision Murli> (84332); have you committed to the destination without using 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 scratch. 2. Restore from a backup of the destination directory, one that doesn't include the bad rev, and re-sync to that. 3. Use svndump to dump up to but not including the bad rev, svnload that into a new repository, that's your "repaired" repository. paul 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 it.support_at_praxis-his.com. 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.orgReceived on 2008-02-25 09:39:48 CET |
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.