Can you provide a hex dump of what you just pasted?  At the level the
bug is occurring in, it's important for us to have the actual bytes.

0000000: 4865 7265 2773 2061 6e20 6578 616d 706c  Here's an exampl
0000010: 6520 6f66 2074 6865 2066 6f72 6d61 7420  e of the format 
0000020: 7765 206e 6565 642e 2020 2849 2075 7365  we need.  (I use
0000030: 6420 7878 6428 3129 2074 6f20 7072 6f64  d xxd(1) to prod
0000040: 7563 650a 7468 6973 2e29 0a              uce.this.).

Thanks,

Daniel

lcwakeman wrote on Wed, Oct 27, 2010 at 17:12:33 -0700:
> 
> Using a hex editor, i found the bad node:
> 
> id: hkh-3.0.r3/1147375416.type: file.count: 0.text: 2 18255002 89 76
> a62e181985b9f0188358520286e7f3cf de9e9fa50eb1d5cbaae57a82ddfc20e398a8ed9b
> 2-2/_ki0.props: 3 1147375350 53 0
> 113136892f2137aa0116093................................................ignedDocument.gif.copyroot:
> 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.
> 
> 
> 
> lcwakeman wrote:
> > 
> > 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                      
> >                          
> > ignedDocument.gif
> >  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 ?
> >     options.dumpWindows)
> >   File "fsfsverify.py", line 591, in verify
> >     raise DataCorrupt, \
> > __main__.DataCorrupt: PLAIN data is corrupted.  Expected digest
> > '113136892f2137aa0116093                                               
> > 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
> >>>> svnadmin. 
> >>>> 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:
> >>> http://svn.apache.org/repos/asf/subversion/trunk/contrib/server-side/fsfsverify.py
> >>> 
> >>> 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
> >>> repository.
> >>> Keep a backup of the broken rev just in case!
> >>> 
> >>> If you want to know more details, see:
> >>> http://subversion.tigris.org/issues/show_bug.cgi?id=3705
> >>> 
> >>> There's also been another recent post by Julian Foad about corrupt
> >>> revisions and how he fixed them:
> >>> http://svn.haxx.se/dev/archive-2010-10/0095.shtml
> >>> 
> >>> 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?
> >>> 
> >>> Thanks,
> >>> Stefan
> >>> 
> >>> 
> >> 
> >> 
> > 
> > 
> 
> -- 
> 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.
> 

Reply via email to