From c0bedbaed99834f2f8353d1a6585139ef98d1310 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 26 Jun 2017 12:49:20 -0400 Subject: [PATCH] followup --- ...ment_4_6a5f8590e6a60be5afe6bc6ffce1c94e._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Problem_with_corrupt_SQLite_DB/comment_4_6a5f8590e6a60be5afe6bc6ffce1c94e._comment 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. +"""]]