----- Peter Murray <peter@OhioLINK.edu> wrote:
[snip]
> I am seeing something similar -- my traceback is:
>
> NodeRev Id: rnh.0.r484/1681172
> type: file
> text: DELTA 484 0 1664102 1665064 fe1d84884432f81ebd5a0face0fbca2e
> prop: PLAIN 484 1681080 79 0 c5ace532febc790dbc2ace6a96a9aed0
> cpath: /jpip_server/image.j2c
> copyroot: 0 /
> starting length: 1664098
> offset: 6
> total: 610757
> remaining: 1053341
> Traceback (most recent call last):
> File "fsfsverify/fsfsverify.py", line 699, in ?
> process(noderev, rev_file, options.dump_instructions,
> options.dump_windows)
> File "fsfsverify/fsfsverify.py", line 652, in verify
> dump_windows)
> File "fsfsverify/fsfsverify.py", line 289, in verify
> digest = parse_svndiff(f, self.length, dump_instructions,
> dump_windows)
> File "fsfsverify/fsfsverify.py", line 178, in parse_svndiff
> (instr_size, data_length, target_length_tmp) = \
> File "fsfsverify/fsfsverify.py", line 98, in
> parse_svndiff_instruction
> raise "Invalid instruction found at offset %d" % start
> Invalid instruction found at offset 610780
>
>
> The underlying problem in the repository is reported as:
>
> svnadmin: Invalid diff stream: insn 1 cannot be decoded
>
> > Yes, this does look like a similar bug. Andrew MacKenzie also saw a
> similar
> issue. Can you post a copy of the
> > rev file and send me a link to it privately?
>
> I got the latest version of fsfsverify.pl off of your website and that
> didn't
> resolve the problem. Would a copy of the rev file causing this be of
> use to you?
Yes.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jun 30 02:23:05 2006