diff --git a/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_6_58997665e5aa0a237a3ec90efca92891._comment b/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_6_58997665e5aa0a237a3ec90efca92891._comment
new file mode 100644
index 0000000000..70ecee7b9a
--- /dev/null
+++ b/doc/bugs/some_annex_addurl_--fast_--with-files_--json_--json-error-messages_--batch__do_not_quit/comment_6_58997665e5aa0a237a3ec90efca92891._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 6"
+ date="2020-10-12T16:00:31Z"
+ content="""
+Thank you Joey for the analysis!  I am not 100% certain why that nose fork process came about.  May be nose (testing framework) causes a fork if some processes are still lingering after a test completes...  I guess something for us to keep in mind
+
+Also I
+- [identified the change has caused the issue to disappear](https://github.com/datalad/datalad/pull/5013#issuecomment-707189474) while looking through recent datalad changes.  Not yet sure if that was anyhow a \"fix\" but at least I do not observe it any longer
+- reproduced the issue with elderly 7.20190819+git2-g908476a9b-1~ndall+1, so it confirms that it is not a regression within git-annex (due to some flaky run I thought about possible regression).
+
+I think you can close it, and we (datalad) should keep an eye on nose and real-life if any stalls... so far I only observed datalad abandoning `git-annex` process without waiting long enough (like in the original case I reported here) when it could be just taking longer to complete indeed.
+"""]]
diff --git a/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_2_f8ff4c8663d8b7bb30f7b7763be33501._comment b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_2_f8ff4c8663d8b7bb30f7b7763be33501._comment
new file mode 100644
index 0000000000..f4b7420fbb
--- /dev/null
+++ b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_2_f8ff4c8663d8b7bb30f7b7763be33501._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="mhauru"
+ avatar="http://cdn.libravatar.org/avatar/2532433a0207ba772e6ca964e61899c0"
+ subject="comment 2"
+ date="2020-10-12T17:07:58Z"
+ content="""
+Thanks for trying to help! `git status` on the repo that's missing files (and has old versions of some other files, I just noticed) shows nothing remarkable: Some staged modifications, some other unstaged ones, and some untracked files, but they don't include the missing and/or out-of-date ones.
+"""]]
diff --git a/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_3_682cb114d133713f80bdda97a4435a5e._comment b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_3_682cb114d133713f80bdda97a4435a5e._comment
new file mode 100644
index 0000000000..17bc5e103e
--- /dev/null
+++ b/doc/forum/git_annex_repair_--force_fails_without_explanation/comment_3_682cb114d133713f80bdda97a4435a5e._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Lukey"
+ avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b"
+ subject="comment 3"
+ date="2020-10-12T17:20:37Z"
+ content="""
+Hmm, is the broken repo actually on the same branch and same commit as a healthy repo?
+"""]]