Oh, and, just in case it is relevant...
The revision that verify is choking on (that was part of what we restored
from backup) is some 400 revisions ago. So the notion that this file was in
some state of flux at the time the backup was run on Friday seems unlikely
at best.
Dave
----- Original Message -----
From: "Dave Jenkins" <n1mxv@hotmail.com>
To: "Ryan Schmidt" <subversion-2007b@ryandesign.com>
Cc: <users@subversion.tigris.org>
Sent: Thursday, October 25, 2007 11:24 AM
Subject: Re: Corruption problems
> 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
>
> ----- Original Message -----
> From: "Ryan Schmidt" <subversion-2007b@ryandesign.com>
> To: "Dave Jenkins" <n1mxv@hotmail.com>
> Cc: <users@subversion.tigris.org>
> Sent: Tuesday, October 23, 2007 4:00 PM
> Subject: Re: Corruption problems
>
>
>> On Oct 23, 2007, at 14:23, Dave Jenkins wrote:
>>
>>>> Tell us more about your setup.
>>> Sure, Thanks!
>>>
>>> It has been working flawlessly for 2+ years so I have been loathe to
>>> update subversion.
>>>
>>>> OS
>>> Windows Server 2003
>>> Standard Edition
>>>
>>>> OS version
>>> Hmmm... upgraded to Service Pack 2... YESTERDAY. Suspicious?!?
>>>
>>>> Subversion version,
>>> 1.2.3
>>>
>>>> what media is the repository on (local hard disk, local RAID, NFS,
>>>> SAN), could you have hardware problems (have you run some kind of
>>>> hardware test), etc.
>>> Local NTFS hard drive. (Backed up nightly.)
>>
>> You may want to try accessing a copy of your repository using Subversion
>> 1.4.5, see if that works better. Subversion 1.2.x and earlier aren't
>> supported anymore.
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> 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
Received on Thu Oct 25 19:25:24 2007