highly inaccurate project size shown
Summary
Self-hosted gitlab instance (11.8.0) reports 13.5GB of usage for a project with 170MB consumed in its server git repository, 1MB consumed in its wiki, and 0 LFS files in its history.
Steps to reproduce
Clearly unsure how to trigger the problem. It's possible it occurred around the upgrade to 11.8.0.
Example Project
Unfortunately this project is self-hosted and cannot yet be made public.
What is the current bug behavior?
-
git lfs ls-files --all
reports no files on a checkout of the repo (which has only 1 branch) - Both the checkout and the server copy reports about
170M
when runningdu -sh .
- The wiki reports about
1M
when runningdu -sh
. - There are only 2 4.6MB files available for download from its artifact history in CI/pipelines (100 or so pipelines have run over the history of the project).
What is the expected correct behavior?
These numbers should be pretty close to one another. I don't know if there are other files being counted somewhere else -- aborted pushes that hit file limit, for example?
Relevant logs and/or screenshots
None.
Output of checks
None.
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Debian 8.11 Proxy: no Current User: git Using RVM: no Ruby Version: 2.5.3p105 Gem Version: 2.7.6 Bundler Version:1.16.6 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.5 Go Version: unknown
GitLab information Version: 11.8.0-ee Revision: 002a282 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.11 URL: https://git.ligo.org HTTP Clone URL: https://git.ligo.org/some-group/some-project.git SSH Clone URL: git@git.ligo.org:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: shibboleth, github, google_oauth2
GitLab Shell Version: 8.4.4 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Caveat: this discovered two issues that I fixed. The report below is post-fix.
- Permissions on uploads directory
- Presence of an SSH keypair under
/var/opt/gitlab/.ssh
. It dates to 2016 and I have temporarily moved them.
Expand for output related to the GitLab application check
Checking GitLab subtasks ...
Checking GitLab Shell ...
GitLab Shell: ... GitLab Shell version >= 8.4.4 ? ... OK (8.4.4) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Gitaly ...
Gitaly: ... default ... OK
Checking Gitaly ... Finished
Checking Sidekiq ...
Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Incoming Email ...
Incoming Email: ... Checking Reply by email ...
IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking Incoming Email ... Finished
Checking LDAP ...
LDAP: ... LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab App ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... (lots of numbers) Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.5.3) Git version >= 2.18.0 ? ... yes (2.18.1) Git user has default SSH configuration? ... yes Active users: ... 1196 Elasticsearch version 5.6 - 6.x? ... skipped (elasticsearch is disabled)
Checking GitLab App ... Finished
Checking GitLab subtasks ... Finished
Possible fixes
N/A.