[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

SVN corrupted revision.

From: Andrew MacKenzie <amackenz_at_edespot.com>
Date: 2006-05-18 21:16:01 CEST

It would appear that a revision of a file in our repository has become

A user had 'an issue' adding a .mdb file to the repository (not sure what;
she doesn't remember exactly what happened). But the file did get into the
repo. But then nobody could update to that revision (r7810) getting errors
about reading length line. They were able to delete the file in question
(the .mdb) in r7811, and re-add it in r7812. Now things 'seem' okay, but
any action that involves r7810 gets that same error (a dump, updating to
that revision, diffs against it, etc.).

This is using SVN 1.3.1 running under Apache 2.0.58.

What I would *like* to do at this point is dump everything up to r7809 and
after r7814 to 'cut around' the corruption, then import those into a new
repository. Is this doable? Some of the other files in that revision have
been modified since, would I have to ignore those revisions as well?

Something like the following is what I'm thinking:
svnadmin dump -r 7809 myrepo > dump-0-7809
svnadmin dump -r 7814:head --incremental > dump-7814-head
svnadmin create newrepo
svnadmin import newrepo < dump-0-7809
svnadmin import newrepo < dump-7814-head

// Andrew MacKenzie  |  http://www.edespot.com
// GPG public key: http://www.edespot.com/~amackenz/public.key
// Windows: "Where do you want to go today?"
// Linux: "Where do you want to go tomorrow?"
// FreeBSD: "Are you guys coming, or what?"
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 19 16:54:55 2006

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.