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

Re: Corrupted Repository

From: Vincent QB <vincentqb_at_gmail.com>
Date: Sat, 2 Nov 2013 17:15:05 -0500

Hello again,

The problems appear starting with the version of subversion in Ubuntu 13.10
(version 1.7.9 along with 1.8.4). If I go back to Ubuntu 13.04 (version
1.7.5), the problems disappear. I was able to create a new dump. However,
it crashes in the same way when loading in Ubuntu 13.10.

Could this be a bug in the more recent versions?

On Sat, Nov 2, 2013 at 2:06 AM, Vincent QB <vincentqb_at_gmail.com> wrote:

> Hello,
> 0. I've updated to Ubuntu 13.10 recently. I'm using btrfs since about
> August.
> 1. Very recently, my repository (~90gb) started giving an error when I
> update my checked out copy:
> svn: E160004: Corrupt node-revision '3-2320.0-1861.r2320/7091583216'
> svn: E160004: Found malformed header
> 'g?\229?\143#?\239?\140?\224s?\146G^?\166?\183?\169M-?\206?\168?\165
> /?\244?\216ncIY?\237?\222?\228K?\231?\192"?\181Q?\180?\131?\128 '?\235?\200?\250z?\214F?\1665?\137o#?\131S?\154?\23963I*?\172?\215r?\186E&63''
> in revision file
> 2. When doing svn status, I see four folders with an ! next to them. I can
> svn update the others, but not those.
> 3. svn verify fails with error:
> svnadmin: E160004: Revision file (r776) lacks trailing newline
> 4. When trying to rebuild a copy of my repositories using old backup dump
> files, the process stops with the error
> svnadmin: E185003: Invalid diff stream: insn 0 overflows the target view
> Strangely enough, this repository was most likely a rebuilt of the same
> dump files, and so the process of rebuilding from those dump worked at some
> point in time, before updating.
> 5. My svnsync'ed copy on a much older remote computer runs svn verify
> without errors. [I will not be able to transfer large files from that
> remote computer.] However, I've discovered that all revisions since around
> August (around revision 4000 and up) on that backup have the exact same
> size of a few bytes. I suspect this is an independent problem though.
> What is the recommended course of action to recover a fully functional
> repository? Thank you!
Received on 2013-11-02 23:15:36 CET

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.