Storage Not Found Nfsfile 28 Please Try Again Gitlab

Repositories gone after update. Broken migration to hashed storage.

Summary

Apologies if this has been reported elsewhere. I didn't run into annihilation similar after some searching. I'g reporting the issue being discussed in this forum thread. After upgrading my jitney installation to 13.4.1 all but 3 of my repositories are inaccessible. I see a bulletin that says:

No repository

The repository for this project does not exist.

Relevant logs and/or screenshots

Afterward reading the forum thread, I understand that the issue has to do with the migration from legacy storage to hashed storage. It looks similar 3 of my projects successfully made the transition and the remainder did not.

Hither is a screenshot showing some failed migration jobs:

screenshot

They all neglect with the aforementioned error:

Gitlab::Git::CommandError: 2:NoMethodError: undefined method `relative_path' for cypher:NilClass.

The same fault shows up if I attempt to manually run the migrations using the gitlab-rake commands shown here.

Interestingly, if I use the rake commands to list which projects are on hashed storage vs legacy storage I see that the three repositories that I can access are listed every bit on hashed storage and all of the rest are still on legacy storage.

Results of GitLab surroundings info

Expand for output related to GitLab environment info
# gitlab-rake gitlab:env:info                  

System information System: Ubuntu 18.04 Current User: git Using RVM: no Cherry Version: ii.vi.6p146 Gem Version: 2.7.ten Bundler Version:one.17.iii Rake Version: 12.3.three Redis Version: v.0.nine Git Version: 2.28.0 Sidekiq Version:five.2.9 Go Version: unknown

GitLab data Version: 13.4.i Revision: c90be62bdef Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: PostgreSQL DB Version: xi.7 Using LDAP: no Using Omniauth: yeah Omniauth Providers:

GitLab Trounce Version: 13.vii.0 Repository storage paths: default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-vanquish Git: /opt/gitlab/embedded/bin/git

Results of GitLab awarding Check

Expand for output related to the GitLab application check
# gitlab-rake gitlab:bank check SANITIZE=true Checking GitLab subtasks ...                  

Checking GitLab Crush ...

GitLab Vanquish: ... GitLab Shell version >= 13.7.0 ? ... OK (xiii.7.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API bachelor: OK Redis bachelor via internal API: OK gitlab-beat out self-check successful

Checking GitLab Beat out ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Electronic mail ...

Incoming Email: ... Reply past electronic mail is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yeah Database config exists? ... yes All migrations up? ... yeah Database contains orphaned GroupMembers? ... no GitLab config exists? ... aye GitLab config upwardly to date? ... yep Log directory writable? ... aye Tmp directory writable? ... aye Uploads directory exists? ... yes Uploads directory has correct permissions? ... yeah Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (motorbus-gitlab has no init script) Init script upwardly-to-date? ... skipped (bus-gitlab has no init script) Projects have namespace: ... 3/ane ... yes 3/2 ... yep iv/three ... yes iv/4 ... yes 5/five ... yes 5/half dozen ... yep 5/7 ... yes 5/8 ... yes half-dozen/ix ... yeah 5/10 ... yes 4/12 ... yep five/13 ... yes five/14 ... yes 5/fifteen ... yes two/16 ... yeah 5/17 ... yes 5/eighteen ... aye five/19 ... yes five/20 ... yes five/21 ... yes 5/22 ... yes 5/23 ... yep 5/24 ... aye v/25 ... yes 5/26 ... yeah 5/27 ... yes 5/28 ... aye v/29 ... yes 2/xxx ... yes five/31 ... yes 5/32 ... yes five/33 ... yes 5/34 ... yeah 2/35 ... yes 5/36 ... aye v/37 ... yes 5/38 ... yeah five/39 ... yes 5/40 ... yeah 5/41 ... yeah 5/42 ... yes v/43 ... yep 5/44 ... yep 2/45 ... yes 5/46 ... yes 5/47 ... yes v/48 ... yeah 5/49 ... yeah 3/50 ... yes 5/51 ... yes 5/53 ... yeah 9/54 ... yep 5/55 ... aye 5/56 ... yes v/58 ... yeah v/59 ... yep 5/60 ... aye 5/61 ... yeah two/62 ... yes five/63 ... yeah v/64 ... yes 5/65 ... yes five/66 ... yes five/67 ... yes 5/68 ... yes v/69 ... yes Redis version >= 4.0.0? ... yeah Ruby version >= two.5.3 ? ... yes (2.6.6) Git version >= 2.24.0 ? ... yes (2.28.0) Git user has default SSH configuration? ... yes Active users: ... 3 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... aye All projects are in hashed storage? ... no Try fixing it: Please migrate all projects to hashed storage as legacy storage is deprecated in 13.0 and support will be removed in 14.0. For more than data see: physician/administration/repository_storage_types.medico

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Workaround

This snippet will set up any repositories that are broken as a result of the migration.

Edited by

gaonaaguacce.blogspot.com

Source: https://gitlab.com/gitlab-org/gitlab/-/issues/259605

0 Response to "Storage Not Found Nfsfile 28 Please Try Again Gitlab"

Post a Comment

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel