From ff62042ba3eb8c441636bf509686782615bbbed1 Mon Sep 17 00:00:00 2001 From: "git-annex@17927e6dc041ab425c14217a97a685adf3ecf44f" Date: Wed, 27 May 2020 05:21:35 +0000 Subject: [PATCH] --- doc/forum/dropped_files_keep_coming_back.mdwn | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 doc/forum/dropped_files_keep_coming_back.mdwn diff --git a/doc/forum/dropped_files_keep_coming_back.mdwn b/doc/forum/dropped_files_keep_coming_back.mdwn new file mode 100644 index 0000000000..5e7afc84b1 --- /dev/null +++ b/doc/forum/dropped_files_keep_coming_back.mdwn @@ -0,0 +1,23 @@ +I have the following setup: + +A 'working' repo in the manual group, called WORKING +2 'backup' repos in the backup group, called A & B +A rclone/gdrive repo in the backup group, called GD +numfiles has been set to 3. + +A and B can directly see each-other via SSH and both can contact GD +WORKING can directly connect to A, B, and GD + +I work on a set of files, git annex add them and eventually do a +$ git annex sync A --content + +At some point in time later (manual or chron) A does a git annex sync --content and the files end up in A, B and GD + +At some later point in time, I do a git annex drop of some of the files, and after the locks are done, the files are dropped. + +At yet some later point in time, after working on more files on WORKING, I do the git annex sync A --content again, and the files +that were dropped are pulled back from A. I would expect this if WORKING were a 'client' but it's manual, so it shouldn't be pulling it back + +I've checked and all three of A, B, and GD have the files in question. + +Thoughts?