subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Hopkins" <DHopk...@serck-controls.com.au>
Subject RE: How to fix corrupt revision in repo?
Date Tue, 20 Sep 2011 02:12:43 GMT
> > Daniel Shahaf wrote on Monday, 19 September 2011 9:27 PM:
> > You ought to be able to keep the rest of the history even without
> fixing
> > the brokenness in r192.  (as the file is deleted in HEAD, a checkout
> > should work; and you also have the option of dumping the history
while
> > excluding the problematic file from it (via authz+svnsync/svnrdump
or
> > svndumpfilter).)
> 
> I'll look into the authz+svnsync/svnrdump option. Svndumpfilter
doesn't
> work for me because the 'svnadmin dump' operation fails when it tries
to
> process 192 (before I get a chance to use svndumpfilter to eliminate
the
> bogus file). As far as I can tell svndumpfilter operates on dumpfiles
> that already exist, and can't actually stop svnadmin from trying to
> resolve the bogus node-rev header during the dump process. The
> authz+svnsync solution will hopefully allow me to effectively do that
> filtering at an earlier stage in the pipeline.

For the benefit of anyone else who comes across this message thread in
the future, I thought I'd post a final follow-up message with my
results.

The authz+svnrdump solution *did* work for creating a dumpfile without
references to the corrupted file revision. I ended up setting up a
temporary server where I could set custom authz permissions, and
downloaded a beta SVN 1.7 client so that I could use svnrdump rather
than svnsync (which was much simpler to set up). I've successfully
loaded the purged dumpfile into a new repository which now works with
svnadmin verify, svnadmin dump, svnadmin hotcopy etc.

Thanks once again for all your help (especially the authz+svnrdump
suggestion).

Regards,

David Hopkins
Serck Controls


===== PRIVACY AND CONFIDENTIALITY NOTICE =====
The information contained in this message is intended for the named recipient only.  It may
contain privileged and confidential information.  If you are not the intended recipient, you
must not copy, distribute, take any action in reliance on it, or disclose any details of the
message to any person, firm or corporation. If you have received this message in error, please
notify the sender immediately by reply e-mail and delete all copies of this transmission together
with any attachments.
The views or opinions expressed in this e-mail or any attachment are not necessarily those
of Serck Controls Pty Ltd.
NOTE - You should carry out your own virus checks before opening any attachment.


Mime
View raw message