diff --git a/doc/bugs/use_new_hash_format_on_non-crippled_filesystems/comment_1_d6eaf3b455ba2635a928b37c0360c4eb._comment b/doc/bugs/use_new_hash_format_on_non-crippled_filesystems/comment_1_d6eaf3b455ba2635a928b37c0360c4eb._comment
new file mode 100644
index 0000000000..35f0ca9c1c
--- /dev/null
+++ b/doc/bugs/use_new_hash_format_on_non-crippled_filesystems/comment_1_d6eaf3b455ba2635a928b37c0360c4eb._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2020-06-11T18:05:55Z"
+ content="""
+I think you should simply `git annex adjust --unlock` in that repository.
+Get rid of the symlinks from it, and the case sensitivity issues will, I
+hope, not matter. This is the same thing git-annex automatically does when
+initializating a repo on a crippled filesystem.
+
+The other way would be to set annex.tune.objecthashlower=true, see
+[[tuning]], but that can only be done when setting up a new repository,
+since it makes the lower-case hash be used everywhere. (Which is what I'd do
+if I had a time machine.)
+"""]]