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

Fwd: Re: PLEASE Help with Repository CORRUPTION!

From: Saulius Grazulis <grazulis_at_akl.lt>
Date: 2005-03-24 22:54:39 CET

Subject: Re: PLEASE Help with Repository CORRUPTION!
Date: Thursday 24 March 2005 23:50
From: Saulius Grazulis <grazulis@akl.lt>
To: "Robert S. Sfeir" <yosemitesam@gmail.com>

Hi, Robert,

On Thursday 24 March 2005 20:17, you wrote:

> Ciao Saulius,
> I would love to give you my repo.  It's open source.
> ...
> Let me know what you come up with.
> Grazi mile.

My findings so far:

a) all my svn's segfault (1.1.0, 1.1.1, 1.1.3 and 1.2.x (r13350 text-time
branch) on you repository :/

However, I have only correctly checked 1.1.0 and r13350, others were working
with .so libraries from r13350.

b) I have found out that segfault happens for revisions 376-391, but I can
dump ranges 1-375 and 391-484

c) tried first tried to load the dumps into a new repository, but with
subversion 1.2.x (r13350 text-time branch) the resulting repository causes
svn to segfault upon the 'svn co' :( ('svnadmin verify' says repository is OK,

d) with svn 1.1.0 I managed to create repositories that co, export,
verify and dump correctly!

Also, with svn 1.1.0 from your original repository revision ranges 1-375 and
391-484 can apparently also be extracted.

There seems to be a bug somewhere in version from 1.1.1 upwards... Maybe
connected with attributes? Anybody else noticed such problem?

Saulius Gražulis
Visuomeninė organizacija "Atviras Kodas Lietuvai"
P.Vileišio g. 18
LT-10306 Vilnius
Lietuva (Lithuania)
tel/fax:      (+370-5)-210 40 05
mobilus:      (+370-684)-49802, (+370-614)-36366
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 24 22:53:51 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.