On May 17, 2006, at 13:07, kynn at panix.com wrote:
> I have an svn repository with hundreds of thousands of
> lines of code and about 2-years' worth of comments contained in it.
> Since yesterday, svn has been failing in ***entirely random ways***.
> Every time the only solution I have found has been to scrap the
> current version of the repository, create a brand new repository with
> sysadmin creaet, populate it from a recent repository dump with
> sysadmin load, and repeat the changes done since that dump.
[snip]
> The very helpful replies I have received to my previous posts have
> focused on the details of the examples I have posted (e.g. BDB), which
> is reasonable and understandable, but by now I hope it is clear that
> these details are mostly irrelevant, because they change every time
> and I still get unpredictable failures. The only constant across all
> cases is svn's failure. (Curiously, svnadmin has performed
> consistently throughout.)
The suggestion that BDB is the trouble, and that switching to FSFS
might alleviate it, is not irrelevant. Subversion with the BDB
backend is known to behave ridiculously in some setups. FSFS is known
to behave correctly.
If you have dumped and loaded your repository and still have a BDB
repository that means you are running Subversion earlier than 1.2.0,
because FSFS became the default as of 1.2.0. If that's correct,
please upgrade to the current release, 1.3.1, which probably contains
inumerable fixes.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 17 15:24:56 2006