mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
git-annex/doc/walkthrough/fsck__58___verifying_your_data.mdwn

37 lines
1.4 KiB
Text
Raw Normal View History

update documentation for new, neutered key-value backends 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.
2011-08-28 20:28:38 +00:00
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
global numcopies setting * numcopies: New command, sets global numcopies value that is seen by all clones of a repository. * The annex.numcopies git config setting is deprecated. Once the numcopies command is used to set the global number of copies, any annex.numcopies git configs will be ignored. * assistant: Make the prefs page set the global numcopies. This global numcopies setting is needed to let preferred content expressions operate on numcopies. It's also convenient, because typically if you want git-annex to preserve N copies of files in a repo, you want it to do that no matter which repo it's running in. Making it global avoids needing to warn the user about gotchas involving inconsistent annex.numcopies settings. (See changes to doc/numcopies.mdwn.) Added a new variety of git-annex branch log file, that holds only 1 value. Will probably be useful for other stuff later. This commit was sponsored by Nicolas Pouillard.
2014-01-20 20:47:56 +00:00
[[numcopies|copies]] setting is satisfied for all files.
split the walkthrough and inline back together
2011-02-27 16:45:48 +00:00
# git annex fsck
improve unused command's output Display the name of the remote being checked, with "." for the current remote, echoing the way describe takes that to change its description.
2011-05-29 02:20:22 +00:00
fsck some_file (checksum...) ok
split the walkthrough and inline back together
2011-02-27 16:45:48 +00:00
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
I hope these notes do not make this walkthrough page too big.
2015-08-01 22:29:25 +00:00
If you have a large repo, you may want to check it in smaller steps. You may
start and continue an aborted or time-limited check.
# git annex fsck -S <optional-directory> --time-limit=1m
fsck some_file (checksum...) ok
fsck my_cool_big_file (checksum...) ok
Time limit (1m) reached!
# git annex fsck -m <optional-directory>
fsck my_other_big_file (checksum...) ok
...
Use `-S` or `--incremental` to start the incremental check. Use `-m`
or `--more` to continue the started check and continue where it left
off. Note that saving the progress of `fsck` is performed after every
1000 files or 5 minutes or when `--time-limit` occours. There may be
files that will be checked again when `git-annex` exists abnormally
eg. Ctrl+C and the check is restarted.
Reference in a new issue Copy permalink