Using a hex editor, i found the bad node:
id: hkh-3.0.r3/1147375416.type: file.count: 0.text: 2 18255002 89 76
2-2/_ki0.props: 3 1147375350 53 0
0 /..PLAIN.K 13.svn:mime-type.V 24.application/octet-stream.END.ENDREP.
Note the 48 null bytes. It starts at byte 0x44639000 in the file.
> Couldn't get past the following error:
> NodeRev Id: hkh-3.0.r3/1147375416
> type: file
> text: UNKNOWN 2 18255002 89 76 a62e181985b9f0188358520286e7f3cf
> prop: PLAIN 3 1147375350 53 0 113136892f2137aa0116093
> copyroot: 0 /
> Skipping text rep since it isn't present in the current rev
> Traceback (most recent call last):
> File "fsfsverify.py", line 1141, in ?
> File "fsfsverify.py", line 591, in verify
> raise DataCorrupt, \
> __main__.DataCorrupt: PLAIN data is corrupted. Expected digest
> ignedDocument.gif', computed '113136892f2137aa0116093a524ade0b'.
> The cpath should be:
> cpath: /www/themes/Sunset/images/loadSignedDocument.gif
> Can't open the directory in the repo-browser, original error message.
> lcwakeman wrote:
>> I will give it a try and let you know.
>> TortoiseSVN Version info:
>> TortoiseSVN 1.6.11, Build 20210 - 32 Bit , 2010/09/30 20:36:44
>> Subversion 1.6.13,
>> apr 1.3.8
>> apr-utils 1.3.9
>> neon 0.29.4
>> OpenSSL 0.9.8o 01 Jun 2010
>> zlib 1.2.3
>> The repsitory is a file system repository on a SAN disk. I am using TSVN
>> to keep projects syncronised on my two machines.
>> Stefan Sperling-7 wrote:
>>> On Wed, Oct 27, 2010 at 11:44:06AM -0700, lcwakeman wrote:
>>>> I am getting the following error message when doing a verify using
>>>> I get the same errors doing a SVN Update with TortoiseSVN.
>>>> svnadmin: Corrupt node-revision 'c74-3.0.r3/1150218126'
>>>> svnadmin: Malformed text representation offset line in node-rev
>>>> How do I fix this?
>>> Try the fsfsverify.py script:
>>> Copy the broken revision file to a temporary area.
>>> Run fsfsverify.py -f on that copy until it reports no further errors.
>>> Then check if the revision file works again if moved into the
>>> Keep a backup of the broken rev just in case!
>>> If you want to know more details, see:
>>> There's also been another recent post by Julian Foad about corrupt
>>> revisions and how he fixed them:
>>> We know what the symptoms of the problem are, but we don't know the root
>>> cause yet. To contribute a data point, could you please tell us which
>>> server version and which client versions are you using?
View this message in context: http://old.nabble.com/Corrupt-node-revision%2C-Malformed-text-representation-tp30070050p30072410.html
Sent from the Subversion Users mailing list archive at Nabble.com.
Received on 2010-10-28 02:13:13 CEST