My server was moved and now my SVN repository is completely out of whack - simply off line. No help I can find online seems to do anything useful. The svn command line core dumps when I try to commit or update working copies. svnadmin panics and leaves.
Errors look like total panic from Berkeley DB.
This behaviour is bloody useless. I can't take that kind of risk during a server move - we're not talking OS change or anything just a dumb move. If these are the risks I just to have use something else. Maybe revert to CVS - which throws a lock file problem now and then - but that, I can manage.
Not to be silly, but why are you still using BDB as your svn repository format? That stopped being the recommended backend about three years ago. fsfs is much more stable.
Posted by: JD at November 7, 2007 6:30 PMI Dont Want To Know.
- is the answer to your question. This kind of problem shouldn't be possible. That is a non-goal as far as I'm concerned for a repository.
"I use what my host provides out of the box" is the more general answer.
Sidenote to anybody coming by: Don't ever trust any kind of SVN storage with a backup in SVN dump format.
Raw backups are apparently non-robust.