PageRenderTime 6ms CodeModel.GetById 1ms app.highlight 3ms RepoModel.GetById 1ms app.codeStats 0ms

Markdown | 43 lines | 33 code | 10 blank | 0 comment | 0 complexity | a0a529c04870553cf9cbb6b7644e3f2c MD5 | raw file
 1# Repository checks
 3> [Introduced][ce-3232] in GitLab 8.7. It is OFF by default because it still
 4causes too many false alarms.
 6Git has a built-in mechanism, [git fsck][git-fsck], to verify the
 7integrity of all data committed to a repository. GitLab administrators
 8can trigger such a check for a project via the project page under the
 9admin panel. The checks run asynchronously so it may take a few minutes
10before the check result is visible on the project admin page. If the
11checks failed you can see their output on the admin log page under
14## Periodic checks
16When enabled, GitLab periodically runs a repository check on all project 
17repositories and wiki repositories in order to detect data corruption problems. 
18A project will be checked no more than once per month. If any projects
19fail their repository checks all GitLab administrators will receive an email
20notification of the situation. This notification is sent out once a week on
21Sunday, by default. 
23## Disabling periodic checks
25You can disable the periodic checks on the 'Settings' page of the admin
28## What to do if a check failed
30If the repository check fails for some repository you should look up the error
31in repocheck.log (in the admin panel or on disk; see
32`/var/log/gitlab/gitlab-rails` for Omnibus installations or
33`/home/git/gitlab/log` for installations from source). Once you have
34resolved the issue use the admin panel to trigger a new repository check on
35the project. This will clear the 'check failed' state.
37If for some reason the periodic repository check caused a lot of false
38alarms you can choose to clear ALL repository check states from the
39'Settings' page of the admin panel.
42[ce-3232]: "Auto git fsck"
43[git-fsck]: "git fsck documentation"