From 59b62e13f9365fa8a7b1e1997f8fb57ff59cdf1e Mon Sep 17 00:00:00 2001 From: nobodyinperson Date: Wed, 27 Dec 2023 07:50:49 +0000 Subject: [PATCH] Added a comment: Try anex.queuesize and --not --in --- ...omment_4_6f537c4909bb53ca036b0f85833672e1._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment diff --git a/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment b/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment new file mode 100644 index 0000000000..63f4a2e7e0 --- /dev/null +++ b/doc/forum/What_operations_are_safe_to_interrupt__63__/comment_4_6f537c4909bb53ca036b0f85833672e1._comment @@ -0,0 +1,11 @@ +[[!comment format=mdwn + username="nobodyinperson" + avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5" + subject="Try anex.queuesize and --not --in" + date="2023-12-27T07:50:49Z" + content=""" +Git annex can normally resume any operation seamlessly. It can resume from aborted copying and shouldn't need to start over. I suggest: + +- setting [annex.queuesize](https://git-annex.branchable.com/git-annex/) to a low value to commit more frequently to the `git-annex` branch (I think that it does that) +- skipping already-present files by specifying `git annex --copy --to=slowremote --not --in=slowremote`, that should speed up the initial phase of finding what to copy and also not display the files that are already copied (maybe that confused you) +"""]]