Direct transer extraction path setting

How to Use GitLab Migrations
1

Problem to solve

Direct transfer (migration from one Gitlab server to another) causing error “No space left on device”. Direct transfer currently using system “/tmp” directory to temporary hold and extract the imported data which used up all the available system disk space on a large project group.

How can we configure direct transfer (migration) to use a larger mounted block volume?

We have tried:

gitlab_rails['env'] = {
‘TMPDIR’ = ‘/path/to/mounted_bv/tmp’

}

gitlab_rails[‘shared_path’] = ‘/path/to/mounted_bv/tmp’

Steps to reproduce

Perform migration (direct transfer) a large projects group to a limited space gitlab server.

Configuration

Direct transfer enabled

Versions

Transfer from GitLab Enterprise Edition v17.11.6-ee to GitLab Community Edition v17.11.4

  • Self-managed
  • GitLab.com SaaS
  • Dedicated

Versions

Helpful resources

  1. Check the FAQ for helpful documentation, issues/bugs/feature proposals, and troubleshooting tips.
  2. Before opening a new topic, make sure to search for keywords in the forum search
  3. Check the GitLab project for existing issues. If you encounter a bug, please create a bug report issue.
  4. Review existing troubleshooting docs.

Thanks for taking the time to be thorough in your request, it really helps! :blush: