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

Repository corruption: "Could not get next bucket brigade"

From: Samuel Langlois <slanglois_at_ilog.fr>
Date: 2006-12-11 09:28:11 CET

Hello,

I just had a very scary experience with Subversion.
After one of our developers committed a binary file (about 5 MB),
any svn update, cat or export on this file failed with the message:
svn: Malformed representation header

However, "svn info" on the remote URL worked correctly.
I deleted the file using "svn delete" remotely, and it succeeded
(and fixed our continuous integration!). Now, svn update on the folder succeeds.
But I'm a bit reluctant to commit this file again...

I had a look on the server error_log, and found this related to the commit:
[Fri Dec 08 10:54:00 2006] [error] [client 172.16.15.46] Could not get next bucket brigade [500, #0]

Then, every try to update the file gave those errors:
[Fri Dec 08 10:55:17 2006] [error] [client 172.16.1.53] Provider encountered an error while streaming a REPORT response. [500, #0]
[Fri Dec 08 10:55:17 2006] [error] [client 172.16.1.53] A failure occurred while driving the update report editor [500, #160004]
[Fri Dec 08 10:55:17 2006] [error] [client 172.16.1.53] Malformed representation header [500, #160004]

Even now that I deleted the file, I still get the following errors:
[Fri Dec 08 15:20:32 2006] [error] [client 172.16.1.53] File not found: revision 66521, path
'/JRules/trunk/integration/online-help/resonlinehelp.ear' [404, #160013]
[Fri Dec 08 15:20:32 2006] [error] [client 172.16.1.53] A failure occurred while driving the update report editor [500, #160004]
[Fri Dec 08 15:20:32 2006] [error] [client 172.16.1.53] Malformed representation header [500, #160004]

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 kind help!

Samuel

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 11 09:28:19 2006

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