up vote 1 down vote favorite
share [g+] share [fb]

The message for svnadmin dump is svnadmin: malformed file. However svnadmin verify does not report any errors at all. I searched through a few backups and did a binary comparison of the repositories with winmerge (which is binary and actually compares the contents, not just the file dates). In my backup that was made 1 day after the revision was created I did not find any differences. So I don't think the file became corrupted on disk over time. So what can I do now? Btw, this is certainly a bug in SVN because verfiy does not find the error.

link|improve this question
20% accept rate
feedback

2 Answers

up vote 1 down vote

I have seen the issue you have described, because I use FSFS rather than BDB as long as I can identify where the corruption has occurred I can edit the text files to correct the inconsistency, this has worked for svnadmin verify positive and negative corruption.

I host Subversion through Apache with mod_dav_svn, more than once it has been suggested that it could be an Apache threading issue.

link|improve this answer
I opened the text file but I do not know what inconsistency is present. It must be like a single bit because it looks ok. It is not complete garbage. – usr Feb 27 '10 at 21:45
The times it has happened to me it has been glaring, i.e. the revision field that should contain a number containing a date, or a date field set to 1970-01-01. – Richard Slater Feb 28 '10 at 8:39
feedback
up vote 0 down vote

This error still occurs when doing a dump for each version?

Your disks health is ok? There are no I/O error?

link|improve this answer
I took a backup one day after the revision in questions (about 6 month ago) and this backup is still identical to the current repo as far as the rev files are concerned. – usr Mar 3 '10 at 22:06
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.