Git clone or pull becoming slower for repositories

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Git clone or pull for the repositories is becoming slower.

Cause - No free disk space for BITBUCKET_HOME

SCM caching has been disabled due to the machine have less than 5GB (default setting) of free disk space.

Occasionally the Bitbucket Server is reaching resource limits warning is displayed.

The following appears in the atlassian-bitbucket.log

2017-11-24 10:23:32,304 WARN  [ssh-scm-request-handler] username @11Y6RESx623x3139x3 1f57r6a SSH - git-upload-pack 'proj/repo' c.a.util.contentcache.ContentCache content-cache@287: caching has been temporarily disabled because there is not enough space left on /<bitbucket-home>/caches/scm/287

Check if free disk space for BITBUCKET_HOME is less than 5GB


  1. Shutdown Bitbucket Server
  2. Create or edit the file BITBUCKET_HOME/ to set to have a lower value

    It might cause the machine to run out of disk space.

  3. Restart Bitbucket Server


Increase free disk space in the BITBUCKET_HOME directory.

In a data center installation, the caches are located on the local filesystem of each node and not in the shared directory.

Last modified on Aug 8, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.