diff options
| author | Toon Claes <toon@gitlab.com> | 2018-04-23 16:33:18 +0200 |
|---|---|---|
| committer | Toon Claes <toon@gitlab.com> | 2018-05-07 09:42:09 +0200 |
| commit | 7d9191eeff9ceda36d1ee1bea5d1a7e779a9733b (patch) | |
| tree | e44754b13bd77124e6db46c6dbbf7975311ea912 /doc | |
| parent | 583e7fe935f4643540b842009c2e3f6912f44c5f (diff) | |
| download | gitlab-ce-7d9191eeff9ceda36d1ee1bea5d1a7e779a9733b.tar.gz | |
Small documentation reformatting and updates
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/repository_checks.md | 28 |
1 files changed, 17 insertions, 11 deletions
diff --git a/doc/administration/repository_checks.md b/doc/administration/repository_checks.md index ee37ea49874..e3b157ae607 100644 --- a/doc/administration/repository_checks.md +++ b/doc/administration/repository_checks.md @@ -13,12 +13,12 @@ checks failed you can see their output on the admin log page under ## Periodic checks -When enabled, GitLab periodically runs a repository check on all project -repositories and wiki repositories in order to detect data corruption problems. +When enabled, GitLab periodically runs a repository check on all project +repositories and wiki repositories in order to detect data corruption problems. A project will be checked no more than once per month. If any projects fail their repository checks all GitLab administrators will receive an email notification of the situation. This notification is sent out once a week on -Sunday, by default. +Sunday, by default. ## Disabling periodic checks @@ -28,16 +28,22 @@ panel. ## What to do if a check failed If the repository check fails for some repository you should look up the error -in repocheck.log (in the admin panel or on disk; see -`/var/log/gitlab/gitlab-rails` for Omnibus installations or -`/home/git/gitlab/log` for installations from source). Once you have -resolved the issue use the admin panel to trigger a new repository check on -the project. This will clear the 'check failed' state. +in `repocheck.log`: + +- in the [admin panel](logs.md#repocheck.log) +- or on disk, see: + - `/var/log/gitlab/gitlab-rails` for Omnibus installations + - `/home/git/gitlab/log` for installations from source + +Once you have resolved the issue use the admin panel to trigger a new +repository check on the project. This will clear the 'check failed' +state. If for some reason the periodic repository check caused a lot of false -alarms you can choose to clear ALL repository check states from the -'Settings' page of the admin panel. +alarms you can choose to clear *all* repository check states by +clicking "Clear all repository checks" on the 'Settings' page of the +admin panel. --- [ce-3232]: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3232 "Auto git fsck" -[git-fsck]: https://www.kernel.org/pub/software/scm/git/docs/git-fsck.html "git fsck documentation" +[git-fsck]: https://git-scm.com/docs/git-fsck "git fsck documentation" |