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

SVNADMIN Recover and Verify show good but repository still hosed???

From: m christensen <dfs_at_xmission.com>
Date: 2004-11-09 17:57:09 CET

I'm using version previous stable version of SVN ( I see no option to
make it print out its release info)
I'm using version 1.1.0 of TortoiseSVN
The system is running on windows 2K
The repository is in a BDB database.

I have a respository that has a main tree with about a dozen external
repositories for a buch of subdirectories
managed by different groups.

We had a server crash yesterday and lost a network card and connectivity
to our backup network.
As such I have no access to any backups.

BUT... Subversion claims everything is just fine. (it's not fine though)

D:\SVN>svnadmin recover esh_docs
Please wait; recovering the repository may take some time...

Recovery completed.
The latest repos revision is 78.

D:\SVN>svnadmin verify esh_docs
* Verified revision 0.
* Verified revision 1.
---SNIP---
* Verified revision 77.
* Verified revision 78.
D:\SVN>

The fact is any Update Syncs or Creations fail when they hit this
particular directory.

I get :
PROPFIND request failed on '/svn/esh_docs/safety'
PROPFIND of '/svn/esh_docs/safety': 500 internal server error
(http://mis-dev:81)

They have been running fine for several months and there were no changes
aside from an OS
patch for the latest batch of worms.

Ideas, Please!
This is a critical production system and people are getting nervous.

Marc

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 9 17:57:54 2004

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