Unable to Export Project & Best Ways to Control Disk Space?

I have a 500 GB GitLab Server VM. I had it only filled to about 25% Disk Space. However, when I tried exporting a 20 GB Project, all of my VMs ended up breaking. I also had some issues with NGinx ballooning too (I am reverse proxying several VMs), but that is completely unrelated and is in control now after setting harsh Journalling Disk Space Limits (from 16MB to 1MB).

However, since I got GitLab online, the disk space was climbing from 25% to 38%, about 1 GB a minute, and then back down to 27%. Was this perhaps related to trying to Import the 20GB Project to an email? I never did receive the email, so maybe GitLab gave up?

While I’m concerned that I don’t receive an email about the Exported Project in an email, I’m more concerned about controlling the Disk Space inflation that can occur in GitLab.

I tailed the following logs to see if there was anything out of the ordinary. I saw nothing unusual from what I have seen before (I’m not very knowledgable on GitLab keep in mind:

root@gitlab:~# tail -f /var/log/gitlab/gitlab-rails/production.log
root@gitlab:~# tail -f /var/log/gitlab/gitlab-rails/production_json.log

However, the gitlab-cl log is reporting some errors. Maybe this is something I need to address?

root@gitlab:~# sudo gitlab-ctl tail | grep error
{“level”:“error”,“msg”:“lstat /var/opt/gitlab/git-data/repositories/+gitaly/cache: no such file or directory”,“storage”:“default”,“time”:“2020-06-06T02:01:59Z”}
{“level”:“error”,“msg”:“lstat /var/opt/gitlab/git-data/repositories/+gitaly/cache: no such file or directory”,“storage”:“default”,“time”:“2020-06-06T02:11:59Z”}
{“level”:“error”,“msg”:“lstat /var/opt/gitlab/git-data/repositories/+gitaly/cache: no such file or directory”,“storage”:“default”,“time”:“2020-06-06T02:21:59Z”}
==> /var/log/gitlab/nginx/error.log <==
==> /var/log/gitlab/nginx/gitlab_error.log <==
2020-06-06_02:23:01.57274 level=error ts=2020-06-06T02:23:01.572589986Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”
2020-06-06_02:23:02.65397 level=error ts=2020-06-06T02:23:02.65381166Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”
2020-06-06_02:23:03.73295 level=error ts=2020-06-06T02:23:03.732806864Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”
2020-06-06_02:23:04.81238 level=error ts=2020-06-06T02:23:04.812261365Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”
2020-06-06_02:23:05.88934 level=error ts=2020-06-06T02:23:05.889204797Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”
2020-06-06_02:23:06.97059 level=error ts=2020-06-06T02:23:06.970454469Z caller=main.go:717 err=“opening storage failed: block dir: “/var/opt/gitlab/prometheus/data/01E82EJPX9QP38117Z883ZNWS7”: unexpected end of JSON input”

Is this a problem I need to address? Or is that not out of the ordinary? And any recommendations on cleaning up disk space in GitLab or clearing out caches?