From 4f11f9b539f21121ad0f1a4b685b3bfd65ec518b Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnWvnTWY6LrcPB4BzYEBn5mRTpNhg5EtEg" Date: Sat, 1 Aug 2015 22:29:25 +0000 Subject: [PATCH] I hope these notes do not make this walkthrough page too big. --- .../fsck:_verifying_your_data.mdwn | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/doc/walkthrough/fsck:_verifying_your_data.mdwn b/doc/walkthrough/fsck:_verifying_your_data.mdwn index 62e15b6fa5..2400146108 100644 --- a/doc/walkthrough/fsck:_verifying_your_data.mdwn +++ b/doc/walkthrough/fsck:_verifying_your_data.mdwn @@ -14,3 +14,23 @@ 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 + +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 --time-limit=1m + fsck some_file (checksum...) ok + fsck my_cool_big_file (checksum...) ok + + Time limit (1m) reached! + + # git annex fsck -m + 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.