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

Re: Repo "broken"

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Mon, 23 Mar 2009 19:58:08 +0100

Robert Roessler wrote:
> Stefan Küng wrote:
>> Robert Roessler wrote:
>>>> Seems you're using the BDB repository format. That isn't supported
>>>> anymore in TSVN 1.6 (see the release notes).
>>>> You have to convert your repository to FSFS format if you want to keep
>>>> accessing it via file:///
>>> But no, I have *never* [knowingly] set up a repo to use BDB - even my
>>> very first one, which this isn't... if it helps, the .svn file tree in
>>> the repo and WC appears substantially the same as all the other working
>>> repos.
>>> If I need one, is there some definitive test for examining the file
>>> trees of a repo or WC to determine its "format"?
>> In the db folder inside the repository is a file named fs-type. Open it
>> with a text editor. It contains either "FSFS" or "BDB".
>> If you're using FSFS, try running 'svnadmin recover' on it.
> As expected (by me, anyway ;) ), my afflicted repo is indeed FSFS...
> which makes sense, since I create all of them using the same procedure
> and folder-tree template.
> In any case, svnadmin recover gives the same error as the repo browser:
> "Can't open file '...\db\min-unpacked-rev': The system cannot find the
> file specified"
> However, I notice that none of my other repos contains such a file -
> whatever that means.
> BUT, this repo is the only one that contains a "rep-cache.db" file.
> Finally, I note that 4 out of my 6 repos contain a ".../db/format" file
> that looks like this:
> 3
> layout linear
> While 2 of 6 repos (1 working fine, and this messed-up one) have
> 4
> layout sharded 1000
> Is there anything else I can check? Any theories as to how this
> happened? Could it have been a failed attempt at auto-updating the repo
> format with a new client version?

If 'svnadmin recover' also throws an error, that's not a good sign. You
might have to get the repo back from a backup.
Try 'svnadmin dump /path/to/repo > dump.dmp'
and then load it into a new repo.

If that doesn't work either, you have to use a backup (or as on the
Subversion list for help).


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2009-03-23 19:58:55 CET

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

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