Re: Corruption problems - Crisis averted

We were ultimately able to get an older backup from off-site storage and
restore rev 503... along with at least 6 other old revs that subsequently
reported checksum errors on verify. None of the files that were restored
from the older backup report any errors and the repository now verifies
normally (as do all of our others). That would certainly seem to suggest
that hardware issues started to develope between the two weekly full
backups. And were likely the cause of the initial error that started this
whole oddessey. With the new hardware, mirrored drives, and latest updates
we should be all set for now (knock on... particle board?). Though I think
I will still be re-assessing our back-up strategy taking some of Johnathan's
sage council.

Many thanks to those who responded (Miha, Ryan, and Johnathan).
May I never need your help again! :-)

Dave

----- Original Message -----
From: "Miha Vitorovic" <mvitorovic@nil.si>
To: "Dave Jenkins" <n1mxv@hotmail.com>
Cc: "Ryan Schmidt" <subversion-2007b@ryandesign.com>;
<users@subversion.tigris.org>
Sent: Friday, October 26, 2007 3:34 AM
Subject: Re: Corruption problems

"Dave Jenkins" <n1mxv@hotmail.com> wrote on 25.10.2007 17:24:11:

> Ok... we took the opportunity to replace the somewhat dated and
potentially
> suspect hardware.
> It's now a VM on a screaming shiney new box.
>
> I upgraded from subversion 1.2.3 to 1.4.5.
>
> I re-ran the svnadmin verify... same error.
>
> I installed Python and ran fsfsverify.py against the rev that was cited
by
> verify.
> After filtering out a ton of stuff the net result was::
>
> D:> fsfsverify.py db\revs\503
> [...]
> <Svndiff so: 7473866 ver: 0>
>
> Error InvalidInstruction: Invalid instruction found at offset
> 7492432 (EC)
> Try running with -f to fix the revision
>
> D:> fsfsverify.py -f db\revs\503
> [...]
> Copy 224819 bytes from offset 7473870
> Write 224819 bytes at offset 7473866
> Fixed? :-) Re-run fsfsverify without the -f option
>
> D:>fsfsverify.py db\revs\503
> [...]
> Traceback (most recent call last):
> File "fsfsverify.py", line 1126, in <module>
> options.dumpWindows)
> File "fsfsverify.py", line 565, in verify
> svndiff = Svndiff(f, self.length)
> File "fsfsverify.py", line 456, in __init__
> (self.startingOffset)
> __main__.InvalidSvndiffHeader: Invalid svndiff header at offset
> 7473866
>

Well, since you already tried everything else, I suggest you try to
contact the SVN developers. They usually monitor this list anyway, but
obviously haven't picked up on your problem. I also know they try to help
a user in a situation like this, since it helps them to tack down the bugs
as well.

Br,

---
  Miha Vitorovic
  Inženir v tehničnem področju
  Customer Support Engineer
   NIL Data Communications,  Tivolska cesta 48,  1000 Ljubljana,  Slovenia
   Phone +386 1 4746 500      Fax +386 1 4746 501     http://www.NIL.si
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org