diff --git a/doc/forum/Problem_with_corrupt_SQLite_DB/comment_4_6a5f8590e6a60be5afe6bc6ffce1c94e._comment b/doc/forum/Problem_with_corrupt_SQLite_DB/comment_4_6a5f8590e6a60be5afe6bc6ffce1c94e._comment
new file mode 100644
index 0000000000..e1febc1395
--- /dev/null
+++ b/doc/forum/Problem_with_corrupt_SQLite_DB/comment_4_6a5f8590e6a60be5afe6bc6ffce1c94e._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 4"""
+ date="2017-06-26T16:20:29Z"
+ content="""
+In a v6 repository, the sqlite database is used to keep track of unlocked
+files. If all files are locked, the sqlite database can still be deleted
+safely.
+
+I've done some experimentation with deleting the sqlite database when there
+are unlocked files, and it seems that running `git annex fsck` manages to
+recover the deleted state and restores the database.
+"""]]