From d46504e51e01c956a0ebdc993b7c05d045c6f340 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 22 Jan 2025 16:48:51 -0400 Subject: [PATCH] response --- ..._427da1bb31bbbcdb88dce5d253e976cc._comment | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 doc/forum/reuploads_existing_files_to_bare_repo/comment_1_427da1bb31bbbcdb88dce5d253e976cc._comment diff --git a/doc/forum/reuploads_existing_files_to_bare_repo/comment_1_427da1bb31bbbcdb88dce5d253e976cc._comment b/doc/forum/reuploads_existing_files_to_bare_repo/comment_1_427da1bb31bbbcdb88dce5d253e976cc._comment new file mode 100644 index 0000000000..876a18446e --- /dev/null +++ b/doc/forum/reuploads_existing_files_to_bare_repo/comment_1_427da1bb31bbbcdb88dce5d253e976cc._comment @@ -0,0 +1,24 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2025-01-22T20:43:32Z" + content=""" +If the laptop has not pulled from the server since those files were sent to +it, it does not know the server contains the files yet. So it will try to +send them again. Normally this won't result in the same content being +actually sent again, instead for each file it will check if the file is in +the server yet, and when it sees it is, it won't send it again. + +My first guess is that just the network overhead of doing those checks is +what "fills the upstream". + +It is possible that it's actually re-uploading files that the server +already has, without checking it first, which will result in the server +accepting the upload and then throwing it away, since it already has the content. +This can happen eg, if the same file is being sent into a repository from +two other repositories at the same time. But I don't know of any common +situations where it happens. + +So, if you're sure it's doing that, please provide details about what exact +git-annex commands you're running that are causing it to do that. +"""]]