RE: Corrupt Registry again

Jani,

no I never identified the cause of this or the previous error.

In fact, it is impossible to even determine when the corruption
occurred since the normal commit/update cycle didn't expose the
error.
Only a full checkout revealed the error.

"svnadmin verify" reveals no error in my repaired repository or the
new repository I created from a dump of the repaired one. I didn't run
this command on the repository before fixing it.

Perhaps I need to do a verify after each commit?

I have seen no sign of any hardware problems with the host machine
which has been my domain server for several years.

Russell
 

-----Original Message-----
From: Jani Averbach [mailto:jaa@jaa.iki.fi]
Sent: Saturday, 26 February 2005 7:12 AM
To: Thamm, Russell
Cc: 'users@subversion.tigris.org'
Subject: Re: Corrupt Registry again

On 2005-02-25 14:56+1030, Thamm, Russell wrote:
> Hi,
>
> Today when I tried to checkout my source code from the Subversion
> Repository, I got the error:
>
> REPORT request failed on 'svn/ssc/!svn/vcc/default'
> The REPORT request returned invalid XML in the response:
> XML parse error at line 20051: no element found
> (svn/ssc/!svn/vcc/default)
>
> I had the same problem on 13/12/2004.

I didn't find from archives any traces what was the reason for this
first corruption. This is the first incident, right?
http://svn.haxx.se/users/archive-2004-12/0702.shtml

What do you get if you run svnadmin verify on that repository?

> I'm running Subversion 1.1.1 with apache 2.0.52 (ssl 0.9.7e) on WIN
> NT 4.0 SP 6.0. I am using TortoiseSvn 1.1.1 as my client. There
> are three developers using this repository.
>
> Any idea why this keeps happening?

Could you exclude positively any hardware related problems on your
setup?

BR, Jani

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