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

Decompression of svndiff data failed

From: Eugene Krasikov <zhk_at_ngs.ru>
Date: 2006-11-28 12:37:06 CET

Hello.

I use svnsync to mirror my repo. All worked fine for a while, but
today I get error
      svnsync: REPORT request failed on 'http://192.168.77.17/svn'
      svnsync: REPORT of 'http://192.168.77.17/svn': 200 OK
 (http://192.168.77.17)
every time I try to do svnsync sync.

There's
      [Tue Nov 28 16:33:03 2006] [error] [client 192.168.77.85] A
failure occurred while driving the update report editor [500,
#160005]
      [Tue Nov 28 16:33:03 2006] [error] [client 192.168.77.85] Target
path does not exist [500, #160005]
in Apache's error log.

I found out that I got these errors not only from snvsync, but also
from svn co, svnadmin dump, etc.

This happened after we commited a pack of files in the repo in the
separate subfolder, all operations fail only if they access that
subfolder on that commit revision. If I try to access other files, all
work fine.

I tried to use file:// instead http:// and got "Decompression of
svndiff data failed"

svnadmin verify says the same.

I found "Decompression of svndiff data failed" message only in one
file in sources - /libsvn_delta/svndiff.c - in the zlib_decode
function. So, probably data in the repository in the file for this
revision somehow corrupted during or after commit? Am I right or
there's another reason of these errors (I googled, but what I found is
not my case)?

And the most important thing. How can I make my repo consistent back
now? I can't even make svnadmin dump and erase that revision from dump
file...

Thanks,
Eugene Krasikov

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 28 16:09:58 2006

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.