gitlab-org--gitlab-foss/doc/administration/repository_checks.md

49 lines
2.1 KiB
Markdown
Raw Normal View History

---
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-04-06 07:47:05 -04:00
# Repository checks
2016-04-04 11:23:43 -04:00
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/3232) in GitLab 8.7.
2016-04-04 11:23:43 -04:00
Git has a built-in mechanism, [`git fsck`](https://git-scm.com/docs/git-fsck), to verify the
2016-05-30 01:30:16 -04:00
integrity of all data committed to a repository. GitLab administrators
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
checks failed you can see their output on in the [`repocheck.log`
file.](logs.md#repochecklog)
2016-04-04 11:23:43 -04:00
NOTE: **Note:**
It is OFF by default because it still causes too many false alarms.
2016-04-13 05:15:36 -04:00
## Periodic checks
2016-04-04 11:23:43 -04:00
When enabled, GitLab periodically runs a repository check on all project
2018-05-03 15:14:48 -04:00
repositories and wiki repositories in order to detect data corruption.
A project will be checked no more than once per month. If any projects
2016-04-06 07:47:05 -04:00
fail their repository checks all GitLab administrators will receive an email
2018-05-03 15:14:48 -04:00
notification of the situation. This notification is sent out once a week,
2018-09-20 05:10:57 -04:00
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-04-04 11:23:43 -04:00
2016-04-06 06:26:29 -04:00
## Disabling periodic checks
You can disable the periodic checks on the 'Settings' page of the admin
panel.
2016-04-04 11:23:43 -04:00
## What to do if a check failed
2016-04-13 06:20:43 -04:00
If the repository check fails for some repository you should look up the error
in the [`repocheck.log` file](logs.md#repochecklog) on disk:
- `/var/log/gitlab/gitlab-rails` for Omnibus installations
- `/home/git/gitlab/log` for installations from source
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**.