summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar gernot <gernot@web>2016-05-29 13:10:19 +0000
committerGravatar admin <admin@branchable.com>2016-05-29 13:10:19 +0000
commit83c969b49c62bba3a8c4dccf394ab16ff3121640 (patch)
treefe96ad64a28c6dd253e589271be8c6ae1be6d23b
parent5ee2bf08f057c42877391092bfb05eb6aee23051 (diff)
-rw-r--r--doc/forum/Problem_with_corrupt_SQLite_DB.mdwn17
1 files changed, 17 insertions, 0 deletions
diff --git a/doc/forum/Problem_with_corrupt_SQLite_DB.mdwn b/doc/forum/Problem_with_corrupt_SQLite_DB.mdwn
new file mode 100644
index 000000000..7cc2a5ddf
--- /dev/null
+++ b/doc/forum/Problem_with_corrupt_SQLite_DB.mdwn
@@ -0,0 +1,17 @@
+Apparently, I managed to corrupt an SQLite DB when `git-annex get` ran out of space. This prevents git-annex operations from
+working at all now.
+
+For example:
+
+ % git annex find --in .
+ sqlite worker thread crashed: SQLite3 returned ErrorError while attempting to perform prepare "SELECT null from content limit 1": no such table: content
+ git-annex: sqlite query crashed
+
+One of the few mentions of SQLite being used is in incremental fsck
+([[design/caching_database]]). I did run incremental fsck in
+another repository a few days before this. The fsck finished
+without issues, so I'd be happy with a solution that involves simply
+deleting the DB or something.
+
+- git-annex version: 6.20160527-gb7d4774
+- All repositories/remotes: version 5, indirect