diff --git a/doc/bugs/parallel_get_can_fail_some_downloads_and_require_re-getting_/comment_1_1173126bd91dcb7fd13c57f06fd16c2b._comment b/doc/bugs/parallel_get_can_fail_some_downloads_and_require_re-getting_/comment_1_1173126bd91dcb7fd13c57f06fd16c2b._comment
new file mode 100644
index 0000000000..469518202b
--- /dev/null
+++ b/doc/bugs/parallel_get_can_fail_some_downloads_and_require_re-getting_/comment_1_1173126bd91dcb7fd13c57f06fd16c2b._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-05-25T17:29:08Z"
+ content="""
+Let's not diagnose a concurrency problem prematurely.
+
+I've run many concurrent gets and never seen masses of failures, or indeed any
+failures without either an error message explaining why it failed, or something
+obviously wrong (like the drive not being mounted).
+
+The json output is making it harder than necessary to understand what's going on.
+It seems you should be easily able to replicate the same problem without --json.
+"""]]