Permalink
Browse files

fix formating and comments on a test post

  • Loading branch information...
1 parent 93c33cc commit 0a7607dde59bc942ae0fd8b60db160a66826da5a @mdxp mdxp committed Jul 3, 2012
@@ -6,20 +6,25 @@ published: true
slug: svnadmin-cant-open-file-svndbfsfs-conf-no-such-file-or-directory
status: publish
title: 'svnadmin: can''t open file ''svn/db/fsfs.conf'': No such file or directory'
+comments: true
wordpress_id: '1105'
categories:
- svn
- Tips and Tricks
---
While working on setting up a _backup script for a subversion repository_ I encountred an interesting problem. I've done this before many times, on different repos, and haven't seen any issues, but in this case the backup command that is using the built-in **svnadmin hotcopy** command was failing with this error:
-`svnadmin hotcopy --clean-logs /svn/repo/ /backup/repo/
-svnadmin: Can't open file '/svn/repo/db/fsfs.conf': No such file or directory`
+```
+svnadmin hotcopy --clean-logs /svn/repo/ /backup/repo/
+svnadmin: Can't open file '/svn/repo/db/fsfs.conf': No such file or directory
+```
Hmm... looking at the respective path I can see that the command is not lying and that file **fsfs.conf** is indeed not present. I could find a file **fs-type** but not fsfs.conf. So my only assumption was that this is an _older_ repository created with an _older svn version_ than the one we were running currently. Checking the existing svn version I got:
-`svn --version
+```
+svn --version
svn, version 1.6.11 (r934486)
-compiled Apr 20 2010, 00:24:22`
+compiled Apr 20 2010, 00:24:22
+```
and the fact that this repo was very old (~2009) made my assumption sound correct. Ok, now what? Well in this situation my first thought was to use the **svnadmin upgrade** command; from the manual it looked like this is what I needed to fix this issue:
_"svnadmin help upgrade
@@ -37,16 +42,18 @@ integrity of the repository.  It does not guarantee the most optimized
repository state as a dump and subsequent load would."_
After I've made a manual backup archive of the repo (a simple tar.gz of the repo folder) I ran the upgrade command sure this is going to fix my issue:
-`svnadmin upgrade /svn/repo/`
+```
+svnadmin upgrade /svn/repo/
+```
and after it completed, I verified that svn was still working as expected and checked for the fsfs.conf file. But that was **not created**... Hmm... Let's try the hotcopy command anyway:
-`svnadmin hotcopy --clean-logs /svn/repo/ /tmp/repo/
-svnadmin: Can't open file '/svn/repo/db/fsfs.conf': No such file or directory`
+```
+svnadmin hotcopy --clean-logs /svn/repo/ /tmp/repo/
+svnadmin: Can't open file '/svn/repo/db/fsfs.conf': No such file or directory
+```
the exact same error.
Trying to understand what the fsfs.conf file contains I just created a new repository to see if it gets created. Indeed my v1.6.11 of svn created the file for a new repo, and after copying it to the location of my existing repository (as it was basically just an empty file) my issue was fixed and the hotcopy command started working. Here is the content of the file as created by my svn version, that I copied in the older repo to fix this problem:
-
-
<code>cat fsfs.conf
### This file controls the configuration of the FSFS filesystem.
@@ -86,6 +93,4 @@ Trying to understand what the fsfs.conf file contains I just created a new repos
### should be enabled consistently over the life of the repository.
# enable-rep-sharing = false</code>
-
-
Hopefully this will help others seeing the same issue I was experiencing.

0 comments on commit 0a7607d

Please sign in to comment.