diff options
| author |  Joey Hess <joey@kitenet.net> | 2011-02-27 12:45:48 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-02-27 12:45:48 -0400 |
| commit | 98e246b49b3c4fed319fe7bc1e900ba20ebfc9e1 (patch) | |
| tree | ad49ec6baf1b57f3acc8b694bdfc1bbd0986021f /doc/walkthrough/fsck:_verifying_your_data.mdwn | |
| parent | 9e49a71282def0b6d6f7507d59eb0f805c6e0073 (diff) | |
split the walkthrough and inline back together
Diffstat (limited to 'doc/walkthrough/fsck:_verifying_your_data.mdwn')
| -rw-r--r-- | doc/walkthrough/fsck:_verifying_your_data.mdwn | 16 |
1 files changed, 16 insertions, 0 deletions
diff --git a/doc/walkthrough/fsck:_verifying_your_data.mdwn b/doc/walkthrough/fsck:_verifying_your_data.mdwn new file mode 100644 index 000000000..cd3a47a8a --- /dev/null +++ b/doc/walkthrough/fsck:_verifying_your_data.mdwn @@ -0,0 +1,16 @@ +You can use the fsck subcommand to check for problems in your data. +What can be checked depends on the [[backend|backends]] you've used to store +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 + unused (checking for unused data...) 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 |