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

A repository verifying problem

From: Emmanuel Kowalski <emmanuel.kowalski_at_math.u-bordeaux1.fr>
Date: 2005-01-09 21:14:43 CET


  I am using Subversion for version control of my personal files and in
the last days, because of (I think) a hard-drive hardware problem, the
database/repository has been corrupted. Specifically, when running

  # svnadmin verify /home/svnroot

a checksum mismatch is reported at revision 2626. Looking on the web I
found suggestions of changing the checksum in the database to go past
this error, but after some difficulty understanding the instructions and
finally zeroing the MD5 sum, the verification fails with the following

  # svnadmin verify /home/svnroot

  * Verified revision 1.
  * Verified revision 2626.
  svn: Filesystem path 'trunk/tex/livre/sec00.tex' is neither a file
  nor a directory

an error which I didn't find mentioned on the web. In case it matters,
here is my configuration:

        OS: Linux Fedora Core 1 (Pentium 4)

        db4 db4-4.1.25-14.i386.rpm
        db4-devel db4-devel-4.1.25-14.i386.rpm
        db4-utils db4-utils-4.1.25-14.i386.rpm
        subversion subversion-0.37.0-1.i386.rpm
        subversion-devel subversion-devel-0.37.0-1.i386.rpm
        subversion-perl subversion-perl-0.37.0-1.i386.rpm
        subversion-python subversion-python-0.37.0-1.i386.rpm
        subversion-server subversion-server-0.37.0-1.i386.rpm
        subversion-tools subversion-tools-0.37.0-1.i386.rpm

As it turns out, the particular problem with revision 2626 is quite
innocuous (it concerns a single file that was subsequently renamed and
is also contained in a directory which I duplicated after the book it
contained was published, so that the second ``current'' directory
contains files with later corrections, etc, and is the one being
actively used).
However, I have no way at the moment of knowing whether further
revisions also contain corruptions, and the current problem prevents me
from doing backups otherwise than by duplicating the entire svnroot
(instead of dump/load).

So my questions are:
Would there be a way to ``erase'' all trace of the file in revision
2626? Or to correct the ``neither a file nor a directory error'' to
check further revisions?

Thanks in advance for any help, and thanks and congratulations to the
entire SVN team for this very nice tool...


        Emmanuel Kowalski

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 9 21:19:54 2005

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