Hello!
A few weeks ago, our repository became inaccessible. We had two recent
backups, both of which are also not viable. We desperately need to recover
this repository, or at least a recent revision. The last revision was 649.
"svnadmin verify" reports the following:
* Verified revision 0.
...
* Verified revision 299.
svn: No such string 'ol7'
>
Working backward starting from revision 649, I dumped one revision at a
time. For revisions 640-649, "svnadmin dump" reports "No such string
'ol4'." For revisions 618-639, it reports "No such string 'om5'." I have
not tested all of revisions 300-617, but attempts to dump a few revisions
chosen at random from within that range yielded similar results.
"svnadmin recover" reports no errors when applied to the most recent backup,
but a dump file produced from that backup is still not viable when loaded
into a newly-created repository:
...
------- Committed revision 299 >>>
<<< Started new transaction, based on original revision 300
* adding path : Messaging/PABS/PABS_Admin/LDAPmap.fm ... done.
* adding path : Messaging/PABS/PABS_Admin/PABS_3-1_admin.book ... done.
* adding path : Messaging/PABS/PABS_Admin/PABS_3-1_adminIX.fm ... done.
* adding path : Messaging/PABS/PABS_Admin/PABS_3-1_adminTOC.fm ...
done.
* adding path : Messaging/PABS/PABS_Admin/admin.fm ...svn: Premature
end of content data in dumpstream
I also tried running the dump file through svndumpfilter and excluding the
Messaging/PABS/PABS_Admin path, but ran into the same "Premature end of
content data" error.
Any advice? If it makes any difference, almost all the files in our
repository are binary files, mostly Framemaker and image files.
Thanks in advance!
Laurel
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 18 01:12:10 2004