Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,361
Community Members
 
Community Events
176
Community Groups

aborting due to possible repository corruption on the remote side

Edited

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.

1 answer

1 accepted

0 votes
Answer accepted

Solution:

git fsck

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

where I want to  execute this command?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events