2020-10-24 23:57:45 +05:30
---
stage: Create
group: Editor
info: "To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers"
type: reference
---
2016-06-02 11:05:42 +05:30
# Repository checks
2020-05-24 23:13:21 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/3232) in GitLab 8.7.
2016-06-02 11:05:42 +05:30
2020-05-24 23:13:21 +05:30
Git has a built-in mechanism, [`git fsck` ](https://git-scm.com/docs/git-fsck ), to verify the
2016-06-16 23:09:34 +05:30
integrity of all data committed to a repository. GitLab administrators
2016-06-02 11:05:42 +05:30
can trigger such a check for a project via the project page under the
admin panel. The checks run asynchronously so it may take a few minutes
before the check result is visible on the project admin page. If the
2020-05-24 23:13:21 +05:30
checks failed you can see their output on in the [`repocheck.log`
file.](logs.md#repochecklog)
2016-06-02 11:05:42 +05:30
2020-04-22 19:07:51 +05:30
NOTE: **Note:**
It is OFF by default because it still causes too many false alarms.
2016-06-02 11:05:42 +05:30
## Periodic checks
2018-10-15 14:42:47 +05:30
When enabled, GitLab periodically runs a repository check on all project
repositories and wiki repositories in order to detect data corruption.
2017-08-17 22:00:37 +05:30
A project will be checked no more than once per month. If any projects
2016-06-02 11:05:42 +05:30
fail their repository checks all GitLab administrators will receive an email
2018-10-15 14:42:47 +05:30
notification of the situation. This notification is sent out once a week,
2018-12-05 23:21:45 +05:30
by default, midnight at the start of Sunday. Repositories with known check
failures can be found at `/admin/projects?last_repository_check_failed=1` .
2016-06-02 11:05:42 +05:30
## Disabling periodic checks
You can disable the periodic checks on the 'Settings' page of the admin
panel.
## What to do if a check failed
If the repository check fails for some repository you should look up the error
2020-05-24 23:13:21 +05:30
in the [`repocheck.log` file ](logs.md#repochecklog ) on disk:
2018-10-15 14:42:47 +05:30
2020-05-24 23:13:21 +05:30
- `/var/log/gitlab/gitlab-rails` for Omnibus installations
- `/home/git/gitlab/log` for installations from source
2016-06-02 11:05:42 +05:30
2020-03-13 15:44:24 +05:30
If the periodic repository check causes false alarms, you can clear all repository check states by
navigating to **Admin Area > Settings > Repository**
(`/admin/application_settings/repository`) and clicking **Clear all repository checks** .
