1git-annex-fsck(1)           General Commands Manual          git-annex-fsck(1)
2
3
4

NAME

6       git-annex-fsck - find and fix problems
7

SYNOPSIS

9       git annex fsck [path ...]
10

DESCRIPTION

12       With  no  parameters,  this  command checks the whole annex for consis‐
13       tency, and warns about or fixes any problems found. This is a good com‐
14       plement to git fsck.
15
16       With parameters, only the specified files are checked.
17

OPTIONS

19       --from=remote
20
21              Check a remote, rather than the local repository.
22
23              Note  that  by  default, files will be copied from the remote to
24              check their contents. To avoid this expensive transfer, and only
25              verify  that the remote still has the files that are expected to
26              be on it, add the --fast option.
27
28       --fast Avoids expensive checksum calculations (and expensive  transfers
29              when fscking a remote).
30
31       --incremental
32              Start  a  new  incremental fsck pass. An incremental fsck can be
33              interrupted at any time, with eg ctrl-c.
34
35       --more Resume the last incremental fsck pass, where it left off.
36
37              Resuming may redundantly check  some  files  that  were  checked
38              before.  Any  files that fsck found problems with before will be
39              re-checked on resume. Also,  checkpoints  are  made  every  1000
40              files  or every 5 minutes during a fsck, and it resumes from the
41              last checkpoint.
42
43       --incremental-schedule=time
44              This makes a new incremental fsck be started  only  a  specified
45              time period after the last incremental fsck was started.
46
47              The time is in the form "10d" or "300h".
48
49              Maybe  you'd like to run a fsck for 5 hours at night, picking up
50              each night where it left off. You'd like this to continue  until
51              all files have been fscked. And once it's done, you'd like a new
52              fsck pass to start, but no more often than once  a  month.  Then
53              put this in a nightly cron job:
54
55               git annex fsck --incremental-schedule 30d --time-limit 5h
56
57       --numcopies=N
58              Override the normally configured number of copies.
59
60              To verify data integrity only while disregarding required number
61              of copies, use --numcopies=1.
62
63       --all -A
64              Normally only the files in the currently checked out branch  are
65              fscked.  This  option  causes  all  versions  of all files to be
66              fscked.
67
68              This is the default behavior when running git-annex  in  a  bare
69              repository.
70
71       --branch=ref
72              Operate on files in the specified branch or treeish.
73
74       --unused
75              Operate on files found by last run of git-annex unused.
76
77       --key=keyname
78              Use this option to fsck a specified key.
79
80       file matching options
81              The  git-annex-matching-options(1)  can be used to specify files
82              to fsck.
83
84       --jobs=N -JN
85              Runs multiple fsck jobs in parallel. For example: -J4
86
87              Setting this to "cpus" will run one job per CPU core.
88
89       --json Enable JSON output. This is intended to be  parsed  by  programs
90              that use git-annex. Each line of output is a JSON object.
91
92       --json-error-messages
93              Messages  that  would  normally  be output to standard error are
94              included in the json instead.
95

SEE ALSO

97       git-annex(1)
98
99       git-annex-repair(1)
100
101       git-annex-expire(1)
102

AUTHOR

104       Joey Hess <id@joeyh.name>
105
106                                                             git-annex-fsck(1)