File: grok-fsck.1.rst

package info (click to toggle)
grokmirror 1.0.0-1.1~deb9u1
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 296 kB
  • sloc: python: 1,792; sh: 24; makefile: 4
file content (64 lines) | stat: -rw-r--r-- 1,914 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
GROK-FSCK
=========
------------------------------------------
Check mirrored repositories for corruption
------------------------------------------

:Author:    mricon@kernel.org
:Date:      2013-08-22
:Copyright: The Linux Foundation and contributors
:License:   GPLv3+
:Version:   0.4
:Manual section: 1

SYNOPSIS
--------
    grok-fsck -c /path/to/fsck.conf

DESCRIPTION
-----------
Git repositories can get corrupted whether they are frequently updated
or not, which is why it is useful to routinely check them using "git
fsck". Grokmirror ships with a "grok-fsck" utility that will run "git
fsck" on all mirrored git repositories. It is supposed to be run
nightly from cron, and will do its best to randomly stagger the checks
so only a subset of repositories is checked each night. Any errors will
be sent to the user set in MAILTO.

OPTIONS
-------
  --version             show program's version number and exit
  -h, --help            show this help message and exit
  -v, --verbose         Be verbose and tell us what you are doing
  -f, --force           Force immediate run on all repositories.
  -c CONFIG, --config=CONFIG
                        Location of fsck.conf

EXAMPLES
--------
Locate fsck.conf and modify it to reflect your needs. The default
configuration file is heavily commented.

Set up a cron job to run nightly and to email any discovered errors to
root::

    # Make sure MAILTO is set, for error reports
    MAILTO=root
    # Run nightly, at 2AM
    00 02 * * * mirror /usr/bin/grok-fsck -c /etc/grokmirror/fsck.conf

You can force a full run using the ``-f`` flag, but unless you only have
a few smallish git repositories, it's not recommended, as it may take
several hours to complete.

SEE ALSO
--------
  * grok-manifest(1)
  * grok-pull(1)
  * git(1)

SUPPORT
-------
Please send support requests to the mailing list::

    http://lists.kernel.org/mailman/listinfo/grokmirror