diff --git a/doc/bugs/broken_repo_when_inodes_exhausted/comment_1_8ccfac4cea4c54029b96b436ac2114ed._comment b/doc/bugs/broken_repo_when_inodes_exhausted/comment_1_8ccfac4cea4c54029b96b436ac2114ed._comment
new file mode 100644
index 0000000000..c71e59fcd5
--- /dev/null
+++ b/doc/bugs/broken_repo_when_inodes_exhausted/comment_1_8ccfac4cea4c54029b96b436ac2114ed._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-04-27T16:55:36Z"
+ content="""
+Pretty much anything is going to break when you run out of inodes; 
+all the errors shown here are due to the git repository getting
+inconsistent because of it. I don't see any part that's git-annex specific.
+
+Is `git annex repair` able to repair it at all? I'd expect it would be able
+to, as long as `git fsck` reports that there are problems.
+"""]]