Forked repo has a different size

Summary

The forked project has different size with source project. Perhaps the total size count takes into account the size of the attached files in the issue tracker or gitlab doesn't run git gc, git prune for project or something else

Steps to reproduce

Fork some project.

https://gitlab.com/alex7d/gitlab-ce - show size: 477.6 MB

https://gitlab.com/gitlab-org/gitlab-ce - show size: 2.9 GB

Example Project

• https://gitlab.com/alex7d/gitlab-ce
• https://gitlab.com/gitlab-org/gitlab-ce

What is the current bug behavior?

Different size

What is the expected correct behavior?

Same size

Relevant logs and/or screenshots

Output of checks

This bug happens on GitLab.com

changed the description

The reason for this are keep-around refs. These are for internal use of gitlab server and are not available in clones or forks.

Some issues to read: gitlab-ce#48522, gitlab-ce#30358.

Hi @alex7d,

First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time.

We're posting this message because this issue meets the following criteria:

• No activity in the past 3 months (since 2018-07-04T21:03:25.579Z)
• Unlabelled

We'd like to ask you to help us out and determine how we should act on this issue.

If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.

If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks for your help!

/cc Triage specialists @gitlab-org/issue-triage

---

You are welcome to help improve this comment.

added auto updated awaiting feedback labels

@DouweM @axil I think that should probably warrant a proper documentation / FAQ item, what do you think?

@rymai sure! The list I compiled in https://gitlab.com/gitlab-org/gitlab-ce/issues/48522 was taken from https://gitlab.com/gitlab-org/gitlab-ce/issues/36803. Not sure if that has changed in the past year. And since I don't know the internals, if you compile a list (or confirm the existing list is OK), we can place this info somewhere in the admin docs.

added [deprecated] Accepting merge requests label

removed [deprecated] Accepting merge requests label

added devopsfulfillment devopsgrowth labels

added devopssystems groupdistribution labels and removed devopsfulfillment devopsgrowth labels

added devopscreate groupgitter labels and removed devopssystems groupdistribution labels

Setting Category:Gitter based on groupgitter.

added Category:Gitter label

removed Category:Gitter devopscreate groupgitter labels

changed the description

added devopscreate documentation groupsource code labels

added sectiondev label

A customer was inquiring on this. From my test fork example, I can confirm this behavior still exists.

Source project https://gitlab.com/gitlab-org/gitlab-compose-kit: 15.5GiB
Forked project: 2.9MiB

Would this be a matter of updating the documentation with the reasoning behind the difference in repository size? TW @msedlakjakubowski, EM @sean_carroll

I believe this is because not all objects count against the new fork. @vyaklushin can you confirm this?

Would this be a matter of updating the documentation with the reasoning behind the difference in repository size?

This would be a good idea. We can add something in the next milestone.

Adding to %16.6 planning.

Thanks @sean_carroll. Once confirmed, I am happy to work on the documentation and get @msedlakjakubowski's review.

Thank you @dkua1

@dkua1 Yes, it's an expected behavior. We use a deduplication strategy to safe storage space. When fork is created, it doesn't copy all objects from the main project. Instead it gets an access to the object pool that connected to the main project. That explains a size difference between the main project and the fork.

Thanks Vasilii. Docs MR created: !133081 (merged).

@sean_carroll The docs MR (!133081 (merged)) is now merged. I believe we can close this issue.

Thank you @dkua1 @vyaklushin closing this issue.

added customer label

changed milestone to %16.6

@sean_carroll - please see the following guidance and update this issue.

	1 Error
	Please add typebug typefeature, typemaintenance and a subtype label to this issue.

If you do not feel the purpose of this issue matches one of the types, you may apply the typeignore label to exclude it from type tracking metrics and future prompts.

This message was generated automatically. You're welcome to improve it.

Marking as typemaintenance as this is likely a documentation update.

added typemaintenance label

Setting label(s) Category:Source Code Management based on groupsource code.

added Category:Source Code Management label

mentioned in merge request !133081 (merged)

closed