> 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.)
----- 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 2:42 PM
Subject: Re: Corruption problems
>
> On Oct 23, 2007, at 12:06, Dave Jenkins wrote:
>
>> We had a user experience a checksum error on a commit. He tried again
>> and with no error.
>> The next export (performed by the build process) got a checksum error.
>> svnadmin verify then reported a checksum error.
>>
>> We restored the entire repository from a backup that was done just prior
>> to the last successful export/build.
>>
>> Now, after restore, about half way through the revision list svnadmin
>> now reports: svnadmin: Invalid diff stream: insn 6174 cannot be decoded.
>>
>> Any thoughts or suggestions?!?
>
> Tell us more about your setup. OS, OS version, Subversion version, 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.
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 23 21:23:54 2007