bbba6c19bd
Backends are now only used to generate keys (and check them); they are not arbitrary key-value stores for data, because it turned out such a store is better modeled as a special remote. Updated docs to not imply backends do more than they do now. Sometimes I'm tempted to rename "backend" to "keytype" or something, which would really be more clear. But it would be an annoying transition for users, with annex.backends etc.
16 lines
669 B
Markdown
16 lines
669 B
Markdown
You can use the fsck subcommand to check for problems in your data. What
|
|
can be checked depends on the key-value [[backend|backends]] you've used
|
|
for the data. For example, when you use the SHA1 backend, fsck will verify
|
|
that the checksums of your files are good. Fsck also checks that the
|
|
annex.numcopies setting is satisfied for all files.
|
|
|
|
# git annex fsck
|
|
fsck some_file (checksum...) ok
|
|
fsck my_cool_big_file (checksum...) ok
|
|
...
|
|
|
|
You can also specify the files to check. This is particularly useful if
|
|
you're using sha1 and don't want to spend a long time checksumming everything.
|
|
|
|
# git annex fsck my_cool_big_file
|
|
fsck my_cool_big_file (checksum...) ok
|