diff --git a/doc/bugs/unnecessary_work_when_drop_cannot_possibly_succeed.mdwn b/doc/bugs/unnecessary_work_when_drop_cannot_possibly_succeed.mdwn new file mode 100644 index 0000000000..93e3451fcf --- /dev/null +++ b/doc/bugs/unnecessary_work_when_drop_cannot_possibly_succeed.mdwn @@ -0,0 +1,12 @@ +When annex.numcopies is 4, and there are only 4 copies of a file, +`git-annex drop` behaves like this: + + drop me (locking a2...) (locking a3...) (locking a4...) (unsafe) + Could only verify the existence of 3 out of 4 necessary copies + +That is unncessary work, because the drop cannot possibly succeed when +there are not more than numcopies. It should be able to skip locking the +content on remotes and immediately fail. + +A user reported a situation where this happened to a lot of files and +caused rate limiting and slowed down git-annex sync. --[[Joey]] diff --git a/doc/forum/Different_preferred_content_for_subdirs/comment_1_5c1e1e6375360cc9416821085b5a68a8._comment b/doc/forum/Different_preferred_content_for_subdirs/comment_1_5c1e1e6375360cc9416821085b5a68a8._comment new file mode 100644 index 0000000000..27c17c4857 --- /dev/null +++ b/doc/forum/Different_preferred_content_for_subdirs/comment_1_5c1e1e6375360cc9416821085b5a68a8._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2022-02-07T16:18:56Z" + content=""" +You are not supposed to quote the pattern after 'include=' + +So, what your expression actually says is if there is a directory +named `"documents/` that contains files ending in `"`, +to apply `not (copies=archive:4)`. + +I am kind of surprised that the original situation would lead to any churn +though. It seems like, since it knows there are at most 3, copies, and 4 +copies are required, it should be able to skip trying to drop at all. +Instead it does unncessary work. Filed a bug, +[[bugs/unnecessary_work_when_drop_cannot_possibly_succeed]]. +"""]]