Error -3 while decompressing data

[Liam Routt]

We're going to run some more tests today; I'll report the results.

I can report, though, that it shouldn't be a network problem, as my test 
is running entirely on the linux server, with the local branch bound to 
a bzr: branch maintained by the bazaar server on the same machine. That 
eliminated the network connection itself, doesn't it? At least the 
cables etc. as the connection is all local to the one box.

We're going to run the same test on the same OS version on a different 
platform (eg. on a PC with a Core2 Quad CPU rather than the Atom). After 
that we'll try some of the things you've suggested below, to collect as 
much data as we can.

Either way we'll report our findings, and I guess I'll create a 
launchpad bug report for it.

Thanks for the help!

Take care,

Liam Routt
Media Saints

On 13/01/2011 12:23 PM, Martin Pool wrote:
> I think you should go ahead and report it on Launchpad, so we have a record.
>
> It is pretty puzzling.  Normally this error means corruption outside
> of bzr, but the fact that the pack file matches the expected sha means
> it is not filesystem corruption of the kind we normally see.  It's
> possible this is a memory error or a filesystem bug, but then it's
> surprising that it would consistently occur at the same point.  As a
> cheap way to check that, you could run memcheck86 on the server.
>
> It's possible it's actually a problem introduced on the network.
> (I've seen marginal Ethernet cables or switches introduce errors at a
> rate of one per several MB, so that in normal use they seem to work
> but bulk transfers will be corrupt.)  If that's so, then running
> bzr+ssh will probably make ssh detect the problem.  You can also check
> the 'ifconfig' error counters (not always reliable) and try copying a
> large file across ssh.
>
> I'm not clear from your original mail whether you can recreate the
> problem by running the commit just simply in a bzr directory on the
> server machine, or if bzr serve needs to be involved.
>
> What happens if you run the commit commands against a local repository
> on the server?
>
> Hope that helps,