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

Re: corrupted fsfs repository, tools for repair?

From: John Szakmeister <john_at_szakmeister.net>
Date: Fri, 26 Jun 2009 04:36:53 -0400

On Thu, Jun 25, 2009 at 11:38 AM, Dirk Taggesell
<dirk.taggesell_at_proximic.com> wrote:
> 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.

Correct. It doesn't do anything for fsfs.

> 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"?

You did back up the rev like the huge warning told you, right?

> 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.

Your rev can be corrupt in more than one location. fsfsverify only
fixes the first one that it finds. The fact that the number is
changing is actually a good thing. It likely means you have several
repeated blocks.

> 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?

I've seen both sides. I have had to run the tool as much as 9 times
on some revisions because there were that many repeated blocks.

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

Restore from backup probably won't work. If the revision was corrupt
on the way in, then your backup has the corrupted rev as well.
Depending on the situation I've been able to recover the data, or
repair the rev if you have access to the correct revisions of specific
files that are corrupted (e.g., someone still has them in their
working copy, or they've been deployed to a web server so you still
have them around).



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

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