Jeff Rogers wrote:
> I have a zero byte file in my repos/db/revs directory. It is the most
> recent file (number 95 in this case). This is causing all sorts of
> problems with check in.
>
> For example...
>
> svn ci -m "checkin notes"
>
> adding......
> adding.....
>
> Transmitting file data .subversion/libsvn_client/commit.c:817:
> (apr_err=70014) svn: Commit failed (details follow):
> subversion/libsvn_subr/io.c:2132: (apr_err=70014)
> svn: Can't read file '/Users/home/repos/db/revs/95': End of file found
>
> I've tried to run svnadmin recover, which resultes in...
>
> svnadmin recover /Users/home/repos/
> Repository lock acquired.
> Please wait; recovering the repository may take some time...
> subversion/libsvn_fs/fs-loader.c:130: (apr_err=160033)
> svnadmin: Failed to load module for FS type 'bdb'
>
> I'm running a binary of svn and svnserve on Mac OS X, I suspect I'm
> using fsfs, is that what is causing this recover problem?
>
> I can live without what was done in the revision causing the issue, is
> there a way to just back this thing out without making a bigger mess?
I have no idea how this state of affairs could have come about. Revision
files are prepared in a temporary location, than moved into place when
complete.
Anyway, as a workaround, move the broken repository away from where it can
be remotely accessed, edit the repos/db/current file, decreasing the first
number from 95 to 94, then do a svnadmin dump of the repository, create a
new repository, load the dump, copy across any modifications you have made
to the hooks and conf directories, and move the newly reloaded repository
into place.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jul 10 15:34:16 2005