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

Broken Repository always fail while svn commit

From: Mohamed Kasim <msmkasim_at_ften.com>
Date: 2004-08-17 10:02:13 CEST


Recently we had a severe issue with the SVN repository, where Commit
consistently failed. We reverted back to a backup repository and recreated
all developers working copy to be compatible to the new repository.

We use Tortoise SVN Client for repository access under Apache Server in
Windows Environment.

Repository size is currently 1.6 GB (strings)

List of issues :

1. Commit always failed.

When commit fail, tortoise SVN client kind of hang ( time out after some
time). After this failure, the database becomes inaccessible and needs a
SVNADMIN RECOVER procedure to get it back. The broken transaction is listed
when checked up with 'svnadmin lstxns'. Now after recovery the database is
accessible , checkout, updates, check for updates are working fine. But
Commit always go back to step 1.

Any idea ( Probably something happened in the way some folders are deleted
and recreated in some previous revisions. This is the suspected area).

However is there any clue or method to debug this situation ?

2. Backup repository.

Now since the problem persist, we used the backup repository which has data
from some 20 revisions earlier (within 2 hours of the last known good
backup). Now this forced all developers to create a new working copy and
merge their local change

Is there a seemless way to recover this scenario to a backed up repository
with out changing any structural changes to current working copy?



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Received on Tue Aug 17 17:22:24 2004

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