diff --git a/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_1_53b7b0d9093b7ffbf80e1bc33c1bc620._comment b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_1_53b7b0d9093b7ffbf80e1bc33c1bc620._comment
new file mode 100644
index 0000000000..34fa727459
--- /dev/null
+++ b/doc/bugs/Of_identical_files__44___all_but_the_first_copy_are_lost_on_unannex/comment_1_53b7b0d9093b7ffbf80e1bc33c1bc620._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="http://openid.yandex.ru/deletesoftware/"
+ nickname="deletesoftware"
+ subject="duplicate"
+ date="2013-08-16T14:47:24Z"
+ content="""
+It's the same as these:
+
+* http://git-annex.branchable.com/bugs/Large_unannex_operations_result_in_stale_symlinks_and_data_loss/ 
+* http://git-annex.branchable.com/bugs/unannex_removes_object_even_if_referred_to_by_others/
+* http://git-annex.branchable.com/bugs/annex_unannex__47__uninit_should_handle_copies/
+* http://git-annex.branchable.com/bugs/unannex_command_doesn__39__t_all_files/
+
+and (as gernot mentioned) according to those, has a workaround of \"git annex unannex --fast\".  Of course, it's not convenient to need to find a workaround, and to notice a potential dataloss issue…
+"""]]