Hi everybody,
Firstly, I used "fsfsverify.py" (I am willing to propose medal for the
author..)
to analyse failed revision records.
http://www.szakmeister.net/blog/fsfsverify/
However, I had to enclose line:
(rev, offset, length, size, digest) = value.split(' ')
into "try-except" -structure
try:
(rev, offset, length, size, digest) = value.split(' ')
except:
print value
sys.exit()
because in some files the space delimiter had been replaced with "
-sign. WTF...
Secondly, the "fsfsverify.py" could not locate all errors so I searched
the signaled error message
from "fs_fs.c" in Subversion sources. Then I added printf -clauses into
C-code and recompiled Subversion
in order to actually see the offending line in data. I think Subversion
should be modified to always
print out the offending data with the error messages in "fs_fs.c".
str = apr_strtok(NULL, " ", &last_str);
if (str == NULL)
return svn_error_create(SVN_ERR_FS_CORRUPT, NULL,
_("Malformed text rep offset line in node-rev"));
/* OK, we print the error message, but why not print the contents of
variable &last_str too? /pekka */
I had run "svnadmin verify" with v1.4.3 before dumping the FSFS
repository. When I created Berkeley DB
and tried to import dump with v1.4.5 into it I could not. Then I created
FSFS database and I got
checksum errors in revisions done in year 2005! This in my opinion rules
out network errors.
When analysing MD5s I noticed that different files in the same revision
had identical checksums!
I am running SVN in SUSE 8.x and have compiled it always from the sources.
I compile Apache using arp -libraries distributed with SVN and I am
using prefork MPM.
The database is accessed using SSL and, now that I think of it, before I
compiled v1.4.6
I also updated to the latest OpenSSL library; maybe it is related...
-pekka-
Ashwin Basagouda Patil wrote:
> Hi there,
>
> Even I had updated our SVN server from 1.4.3 to 1.4.5 on NOV
> 2007. And we are facing lot problem with the repositories. Most of the
> repositories are corrupted. Mean while I was upgraded it to SSL connection
> [https] with the apache 2.059. I am not sure because of which [SVN OR
> APACHE] versions the repositories are getting corrupting. Even the same
> error message I had put in the last post but I didn’t received any response.
>
> When I tried to commit big size files like >500 MB the connection will
> close by the following error and repository get corrupts.
>
> #####################################################
>
>
> svn: REPORT request failed on '/!svn/vcc/default'
> svn: REPORT of '/!svn/vcc/default': Could not read response body: Secure
> connection truncated
> (https://hood.robosoft.co.in)
>
> ########################################################
>
> And when this error is reported by the repository users, I tried with
> the "svnadmin varify" command and there it gives the error as bellow.
>
> 1. "Checksum mismatch while reading representation"
>
> AND
>
> 2. subversion:~ root# /usr/local/bin/svnadmin
> verify /Volumes/Projects/Subversion/Projects/Medha
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> svnadmin: Decompression of svndiff data failed
> subversion:~ root#
>
> So now I suspect on subversion 1.4.5 version I had upgraded. Around 20 of
> the repositories corrupted. Please can you all give me how I would go
> about it now... ? Is really required to upgrade it to 1.4.6 version?
>
>
>
> Ashwin Patil
>
>
>
>
>
> -----Original Message-----
> From: eg <egoots_at_gmail.com>
> To: Pekka Niiranen <pekka.niiranen_at_pp5.inet.fi>
> Cc: users_at_subversion.tigris.org, Thomas Hemmer <themmer_at_go-engineering.de>
> Date: Tue, 05 Feb 2008 17:08:16 -0800
> Subject: Re: "Checksum mismatch while reading representation"
>
>
>> Pekka Niiranen wrote:
>>
>>> I suspect v1.4.5 since after upgrading (thru svnadmin dump)
>>> my server from v1.4.3 I started getting a lots of MD5 problems.
>>>
>>> After upgrading to v1.4.6 I have had none (knock on wood)
>>>
>>>
>> Well if it was in 1.4.5 then it was likely also in 1.4.4 as the only fix
>> in 1.4.5 was a security fix.
>>
>> 1.4.6 did fix at least one possible repository corruption bug.
>>
>> For details see:
>> http://svn.collab.net/repos/svn/tags/1.4.6/CHANGES
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
>> For additional commands, e-mail: users-help_at_subversion.tigris.org
>>
>>
>
>
> -----------------------------------------------
> Robosoft Technologies - Come home to Technology
>
> Disclaimer: This email may contain confidential material. If you were not an intended recipient, please notify the sender and delete all copies. Emails to and from our network may be logged and monitored. This email and its attachments are scanned for virus by our scanners and are believed to be safe. However, no warranty is given that this email is free of malicious content or virus.
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-06 21:53:30 CET