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

Corrupt FSFS Repository?

From: David Felcan <dfelcan_at_avencia.com>
Date: 2005-09-23 15:44:26 CEST

We are running under Win2k, and our SVN instance (v 1.2.3) is accessed through Apache running on the same server as Subversion. We are using file system repositories.

I attempted to work on a project stored in SVN recently using the TortiseSVN client. I did a "checkout..." and everything was copying happily when:





Error: REPORT request failed on '/svn/MOIS_CityMaps/!svn/vcc/default' 
Error: The REPORT request returned invalid XML in the response: XML parse
error at
Error: line 12335: no element found (/svn/MOIS_CityMaps/!svn/vcc/default) 

Uh-oh. Further attempts to update the working copy resulted in:

Error: REPORT request failed on '/svn/MOIS_CityMaps/!svn/vcc/default' 
Error: Invalid diff stream: insn 1245 cannot be decoded 


Getting on the subversion server and running svnadmin verify resulted in:

* Verified revision 0.
* Verified revision 1.
svnadmin: Can't read length line in file 'e:\svnrepos\MOIS_CityMaps\db\revs\2'

Interestingly, the HEAD revision of this repository is *7*. So perhaps this was corrupted earlier on?
Attempts to dump the repository, export the repository all failed with similar errors.

Other repositories on the same server seem to be ok (check out ok with svnadmin verify).

Any insight on this matter would be appreciated. A copy of the repository can be provided subject to managerial approval (likely ok).

Thank you very much,

_Dave Felcan
Dave Felcan
Software Developer
Avencia Incorporated
p: 802.860.9587
f: 215.925.2663
e: dfelcan@avencia.com
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on Fri Sep 23 16:33:08 2005

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

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