svnadmin verify produces "file not found"

[Stefan Witzel <s....@gmx.net>]

Hi,

when I tried to update from my local svn repository today I got an
assertion failure:

svn:
/tmp/buildd/subversion-1.6.17dfsg/subversion/libsvn_delta/compose_delta.c:165:
search_offset_index: Zusicherung »offset < ndx->offs[ndx->length]« nicht
erfüllt.

I tried svnadmin verify on the repository which complained that a file
was not found:

svnadmin: Datei nicht gefunden: Revision 672, Pfad »/somefile«

In contrast to most similar reports I saw, the missing file is an actual
file from the repository, not some transaction. I do have backups but
none including this revision. I have the file, however. So if there was
a way to get the repository working by purging this file, it would be
good enough for me. Is there a way to do that?

Best,
Stefan

Re: svnadmin verify produces "file not found"

[Daniel Shahaf <da...@elego.de>]

Stefan Witzel wrote on Mon, May 21, 2012 at 12:09:46 +0200:
> Hi,
> 
> when I tried to update from my local svn repository today I got an
> assertion failure:
> 
> svn:
> /tmp/buildd/subversion-1.6.17dfsg/subversion/libsvn_delta/compose_delta.c:165:
> search_offset_index: Zusicherung »offset < ndx->offs[ndx->length]« nicht
> erfüllt.
> 

You should set LC_ALL=C in your environment to get these errors in
English for the list.

> I tried svnadmin verify on the repository which complained that a file
> was not found:
> 
> svnadmin: Datei nicht gefunden: Revision 672, Pfad »/somefile«
> 

Note that this most likely means that a revision _later_ than r672 was
corrupted.  You can determine which from the "* Verified revision N."
outputs of svnadmin.

> In contrast to most similar reports I saw, the missing file is an actual
> file from the repository, not some transaction. I do have backups but
> none including this revision. I have the file, however. So if there was
> a way to get the repository working by purging this file, it would be
> good enough for me. Is there a way to do that?

Create an svnsync copy while accessing the corrupted repository through
svn:// or http:// with authz set to deny read access to the offending
file.

Cheers,

Daniel

Re: svnadmin verify produces "file not found"

[Thorsten Schöning <ts...@am-soft.de>]

Guten Tag Stefan Witzel,
am Montag, 21. Mai 2012 um 12:09 schrieben Sie:

> I do have backups but
> none including this revision. I have the file, however. So if there was
> a way to get the repository working by purging this file, it would be
> good enough for me. Is there a way to do that?

Just copy the file back in place and see if it works. svnadmin verify
is a read only operation and shouldn't do any harm, besides that your
repository already is broken. ;-) For things like that I run svnadmin
verify once a day after I had some file system errors resulting in
loosing some revision files and only recognizing some day later after
the whole file system broke down.

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning       E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme      http://www.AM-SoFT.de/

Telefon.............030-2 1001-310
Fax...............05151-  9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow