Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
7d9191ee
Commit
7d9191ee
authored
Apr 23, 2018
by
Toon Claes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Small documentation reformatting and updates
parent
583e7fe9
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
17 additions
and
11 deletions
+17
-11
doc/administration/repository_checks.md
doc/administration/repository_checks.md
+17
-11
No files found.
doc/administration/repository_checks.md
View file @
7d9191ee
...
...
@@ -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"
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment