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

corrupted fsfs repository, tools for repair?

From: Dirk Taggesell <dirk.taggesell_at_proximic.com>
Date: Thu, 25 Jun 2009 17:38:34 +0200

Dear subversion users,

today I ran in a problem with my repository. The server is
Mac OS X 10.4, subversion and apache are from the macports,
the repository is accessed via apache and mod_dav_svn v. 1.4.0
The repository stores data as FSFS.

There has been an undetected filesystem error on the volume
with the repository, corrupting it.

Now if I want to check out, I receive errors like this:
"svn: REPORT of '/svn/repo/!svn/vcc/default': Could not read
 chunk delimiter: Secure connection truncated"

I copied the repository over to my Mac and tried to repair it
using the current macports subversion 1.6.3.

First I inspected the repository and "svnadmin verify" tells me:
--- snip ---
* Verified revision 0.
* Verified revision 1.
* Verified revision 2.
* Verified revision 3.
* Verified revision 4.
* Verified revision 5.
* Verified revision 6.
svnadmin: Invalid diff stream: insn 2403 cannot be decoded
--- snap ---

A svnadmin recover seems to find nothing:
--- snip ---
Repository lock acquired.
Please wait; recovering the repository may take some time...

Recovery completed.
The latest repos revision is 17985.
--- snap ---

But it appears that it actually repairs nothing. As far as
I've read the recover command is mainly for repositories using
Berkeley db.

Anyway, I then downloaded Mr. Zakmeisters fsfsverify, but I'm
not entirely sure how to use it properly.

So svnadmin verify stops at revision 6 and complains about
"insn 2403". Does that mean that revision 7 is corrupt and i
should run "fsfsverify.py -f svn/repo/db/revs/7"?

After doing this, fsfsverify tells me: "Fixed? :-) Re-run
fsfsverify without the -f option" and once I do this, it gives
me an "Error InvalidWindow: ..." all the time, after each repair
run with a different number.

Does this mean, I simply have to run it again and again until the
error is gone? Or is the tool at its wit's end? And the repository
corrupted beyond repair?

Is there anything else (other than restore from the backup) I can do to
recover the repository?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-26 10:00:59 CEST

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