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

Re: Repository corruption: "Could not get next bucket brigade"

From: John Szakmeister <john_at_szakmeister.net>
Date: 2006-12-23 21:12:12 CET

----- Samuel Langlois <slanglois@ilog.fr> wrote:
> We are using svn 1.3.2 on Linux, exclusively through the http://
> protocol
> (Apache/2.2.2 (Unix) mod_ssl/2.2.2 OpenSSL/0.9.7a DAV/2 SVN/1.3.2)
> The repository format is fsfs.
> The whole repository is rather big (several GB, 66,000 revisions);
> it is coming from a CVS import through cvs2svn.
> It is the first time we encounter such a problem in six months of
> work.
> Is there anything that I can look at to help diagnose the problem
> further?
> Is this a known issue?
> How can I be sure that this does not happen again?
> Thanks for your help

It is a known issue, and I believe it has been fixed in the latest version (1.4.2).

As for fixing the problem, have a look at fsfsverify. A number of people have been able to successfully recover their repositories with it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Dec 23 21:12:45 2006

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

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