diff --git a/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment b/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment
new file mode 100644
index 0000000000..6c7b8e2689
--- /dev/null
+++ b/doc/bugs/__34__invalid_object__34___errors_cropping_up/comment_1_d146a64ef8d76c2a7e45bf85d8943456._comment
@@ -0,0 +1,17 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-05-23T16:52:23Z"
+ content="""
+Try running `git fsck` and see if it complains about a corrupt object file.
+You may then need to delete the object file and fix up the repository to
+not refer to it. `git annex repair` can probably handle that.
+
+> Some object in the broken repo seems to be causing this issue somehow.
+
+Maybe, but you also say that the object it complains about has varied.
+Perhaps you have multiple corrupt objects in the git repo..
+
+You mention "litelog". What is that and how is it relevant? Is Android
+involved somehow?
+"""]]