[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

svnadmin dump: Can't set position pointer in file '.../db/revs/148': Invalid argument

From: Olivier Lange <wire_at_petit-atelier.ch>
Date: 2007-01-11 17:33:29 CET

Hi again,

Thanks to the list, I could fix the 'checksum mismatch' I encountered
with a broken repository [1].

A few revisions later, I ran into another issue: "Can't set position
pointer in file ...: Invalid argument", still trying to checkout a
repository with a few broken revisions.

The repository youngest revision is 193, and the "can't set position
pointer" error happens at revision 148:

   .../svnroot$ svnadmin verify lili.bkp
   [...]
   * Verified revision 147.
   svnadmin: Can't set position pointer in file 'lili.bkp/db/revs/148':
Invalid argument

Now the corresponding revision file content is null:

   .../svnroot# lll lili.bkp/db/revs/148
   -rw-r--r-- 1 www-data staff 0 2006-05-15 00:13 lili.bkp/db/revs/148

I found two other null revision files, 151 and 152:

   .../svnroot# find lili.bkp/db/revs -empty -print
   lili.bkp/db/revs/148
   lili.bkp/db/revs/151
   lili.bkp/db/revs/152

Is there a way to fix these revisions, so that I can dump the repository?

Would it be possible to craft a valid "placebo" revision file (a
revision doing "nothing", or some benign update), to replace the
corrupted revision file?

I already had such problem once, detected it immediately, deleted the
revision and revprops, updated the db/current file, made a dumb update
directly on the repository-side, which brought me in sync with the WC
latest revision number. But here, this null revision got into the
repository months ago and does not concern the latest revision.

Kind regards,

--
Olivier
[1] http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=60428

Received on Fri Jan 12 00:14:08 2007

This is an archived mail posted to the Subversion Users mailing list.