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

Invalid diff stream: insn 4 cannot be decoded

From: <Chuck.Berg_at_unlv.edu>
Date: 2007-06-06 18:58:06 CEST

I’m using Subversion here at UNLV to manage all of the course content
we’re developing. The repository is hosted on a RAID 5 subsystem, and one
of the drives was having problems for a couple of days without my knowing
about it. It finally died completely yesterday. I was able to replace the
drive, resynchronize the RAID, recover the file system with chkdsk, and
resolve all but one subversion complaint.

What I'm left with is this: both “svnadmin verify” and “svnadmin dump”
report “Invalid diff stream: insn 4 cannot be decoded” on revision 64.
However, it's important to note that revision 64 was committed several
weeks before the hardware problems started to occur, so I don't know that
they're related.

I tried specifying revisions beyond 64, but that didn't help - I still get
the same error. I also checked both the "dev" and "users" archives, and
while there have been numerous postings about this problem, I did not find
any solutions.

Any new insights from anyone?

Chuck Berg - GSA Affiliate Professor of Gaming Technology
The International Gaming Institute & School of Informatics
University of Nevada Las Vegas
Stan Fulton Building - Room 227
4505 Maryland Parkway · Box 456037
Las Vegas, Nevada 89154-6037
Office: 702-895-5905 · Fax: 702-895-1135

Received on Wed Jun 6 18:58:30 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.