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?
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!
+"""]]