I've been trying to migrate from VSS to Subversion. I've gotten my
migration script working pretty well, but invariably, after so many
"revisions" into Subversion, I get this error, and the whole thing shuts
down. I then have to go to the SVN server and do a "svnadmin recover"
on the db. Fortunately, I can restart my script where it left off (I
finally got this ability somewhat added in), but it will run for a while
longer and again throw this error.
Quite frankly, I'm losing my faith in Subversion/BerkeleyDB. I was
getting these errors in Subversion 1.0.2, so I've upgraded to 1.0.3, and
now 1.0.4, and still I get these errors. I also updated my Berkeley DB
to the latest version/patchlevel. I basically have to babysit the
migration. I'm concerned that if/when I ever get our rather large VSS
db converted, that we will have no end to the problems with the system.
Does anyone out there have any ideas why these errors occur? It is
somewhat consistent (only partially), as I've had it die out at revision
1108 about 15-20 times (prior to adding my restart ability). Of course
the exact same files in the same order are being committed. However,
sometimes it flies right by this revision and goes somewhat farther
before throwing the error. I can't give out my VSS db, as that is
intellectual property, but I would be willing to help track down this
problem, if someone is willing to guide me a little.
TIA
Greg Goodrich
Development Manager
MediNotes Corporation
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat May 29 09:32:09 2004