Hi,
I sent this mail to tigris.com last week, instead of tigris.org, which
made it disappear in the void. So here I try again:
I've just starting migrating a few of my company's projects into
Subversion but I ran into a couple of problems. I'm running subversion
0.28.2 on win2k. The client (only me so far) is accessing the repository
residing on the server via Apache 2.0.47.
I created a repos, added a couple of dirs and made a commit. All fine.
Then I copied about 60 megs of source files into a working dir and
issued svn add. Then I committed and watched alot of dots flying by...
After a couple of minutes I got bored so I opened another shell and
issued an svn log in a working dir different from the first. This caused
the newly issued svn command to hang, as did the first commit. They
timed out after a while so I checked on the server. There, the apache
process was using all cpu resources it could get. After 30 mins or so I
killed the process and ran an "svnadmin recover" on the repository. It
completed fine, which made me issue an "svnadmin lstxns", and found an
outstanding transaction 6. But upon issuing an "svnadmin rmtxns
d:\data\subversion 6" I got this message:
-- begin message ---
svn: Berkeley DB error
svn: Berkeley DB error while fetching string length for filesystem
d:/data/subversion/db:
Not enough space
This application has requested the Runtime to terminate it in an unusual
way.
Please contact the application's support team for more information.
--- end message ---
The disk has plenty of space though. After this I cannot list the
outstanding transactions, but have to recover the repos again. I get the
same message every time I try to remove the outstanding transaction.
Any thoughts on this?
Also, shouldn't one be able to perform two accesses to the server
simultaneously? (As I did with commit / log) At the least, the first
commit shouldn't time out, should it?
/ Michael Grundberg
Received on Tue Sep 9 19:25:27 2003