Commit 7d9191ee authored by Toon Claes's avatar Toon Claes

Small documentation reformatting and updates

parent 583e7fe9
...@@ -13,12 +13,12 @@ checks failed you can see their output on the admin log page under ...@@ -13,12 +13,12 @@ checks failed you can see their output on the admin log page under
## Periodic checks ## Periodic checks
When enabled, GitLab periodically runs a repository check on all project When enabled, GitLab periodically runs a repository check on all project
repositories and wiki repositories in order to detect data corruption problems. 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 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 fail their repository checks all GitLab administrators will receive an email
notification of the situation. This notification is sent out once a week on notification of the situation. This notification is sent out once a week on
Sunday, by default. Sunday, by default.
## Disabling periodic checks ## Disabling periodic checks
...@@ -28,16 +28,22 @@ panel. ...@@ -28,16 +28,22 @@ panel.
## What to do if a check failed ## What to do if a check failed
If the repository check fails for some repository you should look up the error 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 in `repocheck.log`:
`/var/log/gitlab/gitlab-rails` for Omnibus installations or
`/home/git/gitlab/log` for installations from source). Once you have - in the [admin panel](logs.md#repocheck.log)
resolved the issue use the admin panel to trigger a new repository check on - or on disk, see:
the project. This will clear the 'check failed' state. - `/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 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 alarms you can choose to clear *all* repository check states by
'Settings' page of the admin panel. 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" [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"
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment