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

Re: Repos corruption questions

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2003-09-29 00:53:00 CEST

Steve Johnson <steve@parisgroup.net> writes:

> Hi All,
> We've been using svn for a while now. We had a db corruption early
> on, but it's been working fine for months. Yesterday, we started
> getting this when trying to do anything with the repository:
> legolas:src> svn update
> svn: RA layer request failed
> svn: PROPFIND request failed on '/tank1/dev/src'
> svn: PROPFIND of '/tank1/dev/src': 500 Internal Server Error
> When I try dumping the repository using 'svnadmin dump', I get this
> error at one of our more recent (maybe the most recent) revisions:
> subversion/libsvn_fs/err.c:188: (apr_err=160007)
> svn: Invalid filesystem transaction name
> svn: no transaction named `fr' in filesystem
> `svn_repository_bogus/db'
> What does this mean? Any ideas as to what caused it?

Well, it literally means that there was no Subversion transaction
record present in the database with the key 'fr'. Unfortunately, the
cause of such a problem is impossible to discern without more data.

You say that all of a sudden you started seeing these PROPFIND
problems -- have your repository access patterns changed at all? Did
someone suffer some other type of failure that set this off? Do the
Apache logs yield interesting info? Was someone naughty and ran
'svnadmin recover' on the database while it was still in use? Can you
bypass the bogus revision with 'svnadmin dump' (for example, if the
dump always fails at revision 92, can you run 'svnadmin dump
--incremental -r93:HEAD /path/to/repos')?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Sep 29 00:54:10 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.