Git LFS Account over data quota

Question

Git LFS Account over data quota

Opened this issue 4 years ago · 6 comments

Getting the following error when cloning the repo:

Error downloading object: devices/accurev/accurevmsg.xml (d1203a9): Smudge error: Error downloading devices/accurev/accurevmsg.xml (d1203a9edc148fa276c6e74fc169980fa80ab06a6c794b5f185120aa81f47654): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Answer 1 · 2020-09-10T10:51:31.000Z

@blookot In case you've not seen this?

Answer 2 · 2020-09-10T11:18:56.000Z

Hi @robrankin
sorry for the latency, should be solved now, if you can confirm?
Thanks
Vincent

Answer 3 · 2020-09-10T12:24:18.000Z

Hi @robrankin
sorry for the latency, should be solved now, if you can confirm?

No problem @blookot , I'm still seeing the error though.

I guess this might be the original RSA account causing the problem?

This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

Answer 4 · 2020-11-29T19:42:57.000Z

@blookot Still over quota, cant clone or use this.

Answer 5 · 2021-03-31T13:20:41.000Z

Still the same.
The devices and latestout are comming with content like

version https://git-lfs.github.com/spec/v1
oid sha256:afc987365ab8c76c197da3bb42312b2cd057ce1a777d391b28594b7053514cd4
size 4431462

Even the zip downloaded from github.

Answer 6 · 2021-04-01T11:32:12.000Z

For those interested, it appears the culprid for the problema was commit 4f1ea81. After that all files were there (even some base files like input/output.conf and the filter*.conf).

Reverting to commit 3ce2e94 solve the issues (git checkout -f 3ce2e94).

For what I've seen the commits after that aren't "essential"...