From 07a726e0fe457022d4b46f4affeeb34b2bdc107d Mon Sep 17 00:00:00 2001 From: jnkl Date: Sat, 25 Jan 2025 11:49:29 +0000 Subject: [PATCH 1/2] Added a comment --- .../comment_2_04946c3d6240ab5a4e0559edab301c1a._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/reuploads_existing_files_to_bare_repo/comment_2_04946c3d6240ab5a4e0559edab301c1a._comment diff --git a/doc/forum/reuploads_existing_files_to_bare_repo/comment_2_04946c3d6240ab5a4e0559edab301c1a._comment b/doc/forum/reuploads_existing_files_to_bare_repo/comment_2_04946c3d6240ab5a4e0559edab301c1a._comment new file mode 100644 index 0000000000..3dc0418920 --- /dev/null +++ b/doc/forum/reuploads_existing_files_to_bare_repo/comment_2_04946c3d6240ab5a4e0559edab301c1a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="jnkl" + avatar="http://cdn.libravatar.org/avatar/2ab576f3bf2e0d96b1ee935bb7f33dbe" + subject="comment 2" + date="2025-01-25T11:49:29Z" + content=""" +I don't think it was the overhead (stopped it at uploaded 30G for a 180G repo). I am in the process of recreating the repo, so I can't give you further information for now. Will come back to you if it happens again. Thanks for your answer and your awesome work! +"""]] From 9d122a8ff50d99add9a157e63ca38d3c8a903e2b Mon Sep 17 00:00:00 2001 From: jnkl Date: Sat, 25 Jan 2025 12:00:20 +0000 Subject: [PATCH 2/2] --- .../Deduplication_between_two_repos_on_the_same_drive__63__.mdwn | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/forum/Deduplication_between_two_repos_on_the_same_drive__63__.mdwn diff --git a/doc/forum/Deduplication_between_two_repos_on_the_same_drive__63__.mdwn b/doc/forum/Deduplication_between_two_repos_on_the_same_drive__63__.mdwn new file mode 100644 index 0000000000..fee3c11b31 --- /dev/null +++ b/doc/forum/Deduplication_between_two_repos_on_the_same_drive__63__.mdwn @@ -0,0 +1 @@ +I run a server and have a 2.5TB repo on a 4TB drive. Right now I have a bare repo for outside connections on it, but thought about a non-bare repo beside this on the same drive for local use. Does git-annex realize the repos are on the same btrfs-volume and uses ```cp --reflink``` while syncing between them?