Issue #3685 resolved

Repository corruption on the remote side

Tatto de Castro
created an issue

Hi,

First I would like to thank you for the great service you delivery. My dev team is finally upgrading to the paid plan, but we are currently having a strange error, every git pull or git clone is returning the same message: "aborting due a possible repository corruption on the remote side".

Bellow follows a test:

{{{ tatto@tattobook3:~/Desktop/teste$ git clone https://bitbucket.org/serverdoin/mercadodetroca.git Cloning into mercadodetroca... Username: Password: remote: Counting objects: 2634, done. remote: Compressing objects: 100% (1659/1659), done. remote: aborting due to possible repository corruption on the remote side. fatal: early EOFs: 11% (290/2634), 124.00 KiB | 113 KiB/s fatal: index-pack failed }}}

The error is always in the same part. We tried a lot of thing but error is always happening.

Can you give us a little help?

Thanks in advance,  Tatto <bitbucket: tatto>

Comments (9)

  1. Dylan Etkin

    Hi Tatto,

    I am sorry to give you the run-around but could you please re-raise this by sending a mail to support@bitbucket.org?

    It is much easier for us to deal with individual repo issues through support.

    Cheers,

    Dylan

  2. Joel Unger staff

    Hi Tatto,

    I'm not sure what to tell you, support@bitbucket.org definitely works and does not respond with a failed delivery. That address is also not associated with a google group.

  3. Anonymous

    How much does this suck? I got here through Google because I'm having the exact same problem. The whole point of having an open issue tracker is so that problems / solutions can be easily found. If the remote repo was corrupted, then that points to a bitbucket problem -- the remote repo should *never* be corrupted, no matter what the clients throw at it.

  4. Kryn

    HOWEVER, I figured out that changing the content of the email I was able to get the message through to support@bitbucket.org ... Specifically, I removed the listing of my other emails from the content of my email.

  5. Log in to comment