aborting due to possible repository corruption on the remote side

[Danyal Iqbal]

I am  unable to clone a repo from  our productive environment whereas the same repo can be cloned from the test environment. for starters i could not find anything difference in the cofiguration of both envionments.

Please help:.

 Production:

git clone http://bitbucket-prod:7990/projects/EWSW-ARCHIVE/repos/pibase.archive/browse

produces following error:

git -c filter.lfs.smudge= -c filter.lfs.required=false -c

diff.mnemonicprefix=false -c core.quotepath=false clone --branch master

ssh://git@bitbucket-prod:7999/ewsw-archive/pibase.archive.git

f:\temp\pibase.archive

Cloning

into 'f:\temp\pibase.archive'...

remote:

aborting due to possible repository corruption on the remote side.

I have tried the folllowing:

1. delete the repo from production
2. clone repo from test env
3. change remote to production
4. push to production
5. try to clone from productions again (fails)
6. recommendations from stack overflow:

7.git config --global pack.window "0"

git config --global pack.windowMemory "100m"

git config --global pack.packSizeLimit "100m"

git config --global pack.threads "1"

8 git clone fails again.

[Danyal Iqbal · Accepted solution]

Solution:

git fsck

git repack -adf --window=200 --depth=200

[Mahadevan P]

where I want to  execute this command?

[Bhavesh Kharwa]

on git server