You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by David Pinto <ot...@otnip.com> on 2011/01/18 06:26:23 UTC

Help With A Corrupt Repository

I have a corrupt repository I could use help with to fix.  When running
svnadmin, this is the result:

[dpinto@hp-elite Desktop]$ svnadmin verify development_repository
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
svnadmin: Revision file lacks trailing newline

When trying to checkout something that is in Rev4, this is result:

[dpinto@hp-elite Desktop]$ svn checkout
file:///home/dpinto/Desktop/development_repository/otnip/home/CDRipper
A    CDRipper/test
svn: Corrupt node-revision 'aza.0.r4/3118938273'
svn: Missing id field in node-rev

If anyone thinks they can get this resolved, I'd be happy to pay a
consulting fee to do so.  I can setup a login via VNC.  Someone's
goodwill would be great, but, this si worth more than relying on
that :-).

Thank you.

Re: Help With A Corrupt Repository

Posted by Stephen Butler <sb...@elego.de>.
On Jan 18, 2011, at 6:26 , David Pinto wrote:

> I have a corrupt repository I could use help with to fix.  When running svnadmin, this is the result:
> 
> [dpinto@hp-elite Desktop]$ svnadmin verify development_repository
> * Verified revision 0.
> * Verified revision 1.
> * Verified revision 2.
> * Verified revision 3.
> svnadmin: Revision file lacks trailing newline
> 
> When trying to checkout something that is in Rev4, this is result:
> 
> [dpinto@hp-elite Desktop]$ svn checkout file:///home/dpinto/Desktop/development_repository/otnip/home/CDRipper
> A    CDRipper/test
> svn: Corrupt node-revision 'aza.0.r4/3118938273'
> svn: Missing id field in node-rev

Hi David,

This sounds like Subversion issue #2453 "FSFS commits >2GB pass but 
fail verify on Linux, with APR patch".

  http://subversion.tigris.org/issues/show_bug.cgi?id=2453

The problem was fixed five years ago, but it's still possible to compile
Subversion in a manner that makes this bug reappear.

Is revision 3 a big one?

Do you still have the files checked in at r3?

Does your OS or distribution have a newer Subversion available, using
APR 1.2?

Regards,
Steve

--
Stephen Butler | Senior Consultant
elego Software Solutions GmbH
Gustav-Meyer-Allee 25 | 13355 Berlin | Germany
fon: +49 30 2345 8696 | mobile: +49 163 25 45 015
fax: +49 30 2345 8695 | http://www.elegosoft.com
Geschäftsführer: Olaf Wagner | Sitz der Gesellschaft: Berlin
Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194