<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=563337) </details> <!--IssueSummary end--> ## Background This is a follow-up from [Follow up on the missing pool repository after archving incident](/gitlab-com/gl-infra/production-engineering/-/issues/27425). ## Objective Investigate why pool repository links are missing in the database while the repositories still exist on disk. ## Tasks - [ ] Investigate why the rails db and disk would be out of sync. What causes the missing link between forks and pool repository. - [ ] Determine if the missing link issue happens only to old projects - [ ] Currently GitLab only checks the DB record if the pool repository is used by other projects. Explore potential ways to bypass this check on GitLab or Gitaly - [ ] Document findings and propose solutions ## Expected outcome A clear understanding of why links are missing and recommendations for preventing pool repository deletion when they're still in use. ## Sources: 1. [Follow up on the missing pool repository after archving incident](/gitlab-com/gl-infra/production-engineering/-/issues/27425) 2. [The issue](https://gitlab.com/gitlab-org/gitlab/-/issues) 3. [Related issue](https://gitlab.com/gitlab-org/gitaly/-/issues/4506) 4. [Related MR](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/89195) <<- this might explain why the link was broken.