diff --git a/doc/bugs/importtree_replaces_files_with_identical_size/comment_3_2b9bdb906043aa84ea6cf0d74a685769._comment b/doc/bugs/importtree_replaces_files_with_identical_size/comment_3_2b9bdb906043aa84ea6cf0d74a685769._comment
new file mode 100644
index 0000000000..28e0eff04f
--- /dev/null
+++ b/doc/bugs/importtree_replaces_files_with_identical_size/comment_3_2b9bdb906043aa84ea6cf0d74a685769._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="michael@ff03af62c7fd492c75066bda2fbf02370f5431f4"
+ nickname="michael"
+ avatar="http://cdn.libravatar.org/avatar/125bdfa8a2b91432c072615364bc3fa1"
+ subject="comment 3"
+ date="2022-03-21T19:10:35Z"
+ content="""
+First of all, thank you very much for the quick fix!
+
+I don't think that Nextcloud rewrote these files as otherwise git-annex would have re-imported them instead of recognizing the exported files. Using stat, I confirm that the replaced files have indeed the exactly same modify time - `Modify: 2021-12-19 22:47:35.988712668 +0100`. I think this is the time when I copied these files from a different directory, as this does not correspond to the modify time of the original files (that I still have). Quite interestingly, the access time of both original files is also the exactly same time, which supports this hypothesis. I can reproduce that copying a couple of small files using cp gives me target files with exactly identical modify times (in fact, all time stamps stat displays are identical). Steps to reproduce:
+
+```
+for i in $(seq 32); do dd if=/dev/urandom of=file${i}.test bs=20k count=1; done
+mkdir d
+cp *.test d/
+stat d/*.test
+```
+
+For me, this reproduces both on ext4 and on tmpfs.
+"""]]