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

Invalid diff stream

From: Byron Zollars <bgz_at_ecpi.com>
Date: Sat, 7 Feb 2009 20:50:16 -0600

I see other posts from SVN users with the "invalid diff stream" error,
but it seems there aren't a lot of solutions.

I have a repository with a few corrupted revisions, and I've been
trying to find ways to repair or workaround the issues.

For example, running verify on one of the corrupted revs yields:

%svnadmin verify -r176 repos
svnadmin: Invalid diff stream: [tgt] insn 0 starts beyond the target
view position

Trying fsfsverify to fix the problem seems to fix things:
%fsfsverify.py -f repos/db/revs/176 >fsfsout

The last line of the fsfsout file is:
Fixed? :-) Re-run fsfsverify without the -f option

But then re-running verify gives a different error.
%svnadmin verify -r176 repos
svnadmin: Invalid diff stream: insn 4 overflows the target view

I have tried dumping from r0:175 into a new repos, then manually
reconstructing r176 from the logs, and then continuing with the dump/
load process from old to new repos, but whenever a later rev tries to
interact with a r175 file or directory (like a modify or move), there
is an error, because the state of r175 is not as expected.

Has anyone out there had ANY success with similar problems???
My confidence in keeping my company's work under SVN is eroding as I
wrestle with this.

BTW, we use svnserve with svn:// access method, and I've noticed that
the corrupted revs seem to have large files that are being added to
the repos.

Thanks in advance!


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-08 07:37:15 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.