Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #8544

Closed
Open
Created Jan 06, 2015 by Administrator@rootOwner

Fork error - NFS

Created by: jmjoly

Hi everyone,

I'm consistently getting the following error when forking a project I have already forked and deleted from my namespace:

 Fork Error!
You tried to fork <namespace> / <project> but it failed for the following reason:
– Fork transaction failed.

My Gitlab runs in 2 instances (active and passive), using NFS storage for repositories.

To reproduce the problem, execute the following steps:

  1. Fork a repository;
  2. Delete the repository from your namespace;
  3. Fork again the repository, it should then fail.

Gitlab doesn't succeed in removing all project folders, as some deleted files are still open (NFS protocol creates .nfs[0..9] files pointing to the inodes to be deleted). The fork error pops up when forking again, because the project folder already exists in the user namespace.

This issue also affects local storage! Even though the project folders can be removed, the deleted files are wasting disk space because the inodes are still being used by the application.

The error appears in GitLab 7.0.0, 7.4.3, 7.5.3, 7.6.2 (Gitlab-shell 2.2.0 and 2.4.0). Has anyone any workaround or solution for this issue? Thanks.

Assignee
Assign to
Time tracking