Roth, Pierre wrote:
Hi,
I am currently running a vss to svn migration of a 30 GB database.
The vss2svn script completed without error and I generated a dump file.
But I could not svnadmin load it completely : The first 17770 revisions
were inserted but the 17771 failed : a 17770-1 transaction file is still
present in my repos and 17771 rev was not commited.
I wonder if this issue comes from the generated dump file (created by
vss2svn) or from my svnadmin load command.
What is the error you received? It's highly unlikely this would be due
to your svnadmin command so it must be a problem with the dumpfile.
Any idea ? Is there a means (command line option ?) to parse this dump
file and look at revision 17770 to verify its format ?
The dumpfile is mostly human-readable but getting that particular
revision out of a 30GB database could be tricky. Depending on the tools
you have available on your platform, searching for a line which begins
with "Revision-number: 17770" will get you close.
toby
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user