comment

diff --git a/doc/forum/Content_not_present_and_get_doesn__39__t_retrieve_it/comment_3_74055eed54696331af07ba1721055562._comment b/doc/forum/Content_not_present_and_get_doesn__39__t_retrieve_it/comment_3_74055eed54696331af07ba1721055562._comment
new file mode 100644 (file)
index 0000000..cff1136
--- /dev/null
+++ b/doc/forum/Content_not_present_and_get_doesn__39__t_retrieve_it/comment_3_74055eed54696331af07ba1721055562._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2022-02-07T16:28:49Z"
+ content="""
+You should not need to fsck regularly. The question is, what happened to
+make those files that git-annex thinks are present go missing. One
+possible way would be if there was an actual data corruption of files on
+the drive.
+
+`git-annex fsck` only mentions `.git/annex/bad/` when it discovers that a
+file's content on disk has gotten corrupted. It then moves it to that
+directory, and mentions that it has. So this makes me think your drive must
+have data corruption.
+"""]]