diff --git a/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn b/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn
index fefa2ebed9..9935528678 100644
--- a/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn
+++ b/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn
@@ -8,6 +8,12 @@ Running fsck on a remote completely drops the file
 * Run `git-annex fsck`
 * git-annex will notice the corruption and completely drop the file from the remote
 
+I expect git-annex to never drop data unless specified as also mentioned in https://git-annex.branchable.com/walkthrough/fsck__58___when_things_go_wrong/
+
+I would rather look at the corrupted file myself and figure out the best course of action instead of losing it completely.
+
+At this point, I'm no longer running fsck on remotes.
+
 
 ### What version of git-annex are you using? On what operating system?
 8.20200309, Mac