Bitbucket Git Clone Failed (LFS over quota)

The clone failed because Git LFS is over quota - the workspace's LFS storage or bandwidth budget is exhausted, so LFS-tracked objects cannot be downloaded. This is an account-quota problem, not a code error.

What this error means

The clone/checkout step fails fetching LFS objects with an over-quota or bandwidth message. The repository checks out its pointers but the actual large files cannot be retrieved.

bitbucket-pipelines

Error downloading object: assets/model.bin
batch response: This repository is over its LFS data quota.

Common causes

LFS storage or bandwidth exhausted

Git LFS has storage and transfer quotas. Once exceeded, LFS object downloads (including during a pipeline clone) are blocked until the quota is raised or usage drops.

Large or frequently fetched LFS objects

Big binaries pulled on every run consume bandwidth quickly, exhausting the budget faster than expected.

How to fix it

Raise the quota or reduce LFS usage

Increase the workspace's Git LFS storage/bandwidth allotment.
Prune large or unused LFS objects to free quota.
Skip LFS in steps that do not need the binaries (set clone: lfs: false).

Disable LFS fetch where not needed

Steps that do not use the large files can skip LFS to save bandwidth.

bitbucket-pipelines.yml

clone:
  lfs: false   # only the steps that need the binaries should fetch LFS

How to prevent it

Monitor Git LFS storage and bandwidth usage.
Skip LFS fetch in steps that do not need large files.
Prune unused LFS objects and avoid committing huge binaries.