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

Re: svn.collab.net intermittent failures

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-04-14 18:13:24 CEST

David Summers <david@summersoft.fay.ar.us> writes:

> I ran 4 instances on a Dual Xeon 1.8Ghz system and all but one instances
> of stress.pl completed normally. Here is the results for the one that
> didn't complete normally:
> Transmitting file data .svn: Item already exists in filesystem
> svn: Commit failed (details follow):
> svn: successor id `0.0.t3' (for `0.0.sy') already exists in filesystem
> '/home/dsummers/rpms/build/subversion-0.20.1/tools/dev/repostress/db'
> svn: Berkeley DB deadlock error
> svn: Berkeley DB error while reading node revision for filesystem
> /home/dsummers/rpms/build/subversion-0.20.1/tools/dev/repostress/db:
> DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock
> unexpected commit fail: exit status: 256

I remember that one. Here is my original report


and here is where Karl reproduced it


I don't remember how (or even if) the problem was resolved.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Apr 14 18:14:18 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.