Joey Hess af254615b2 use WAL mode to ensure read from db always works, even when it's being written to ... Also, moved the database to a subdir, as there are multiple files. This seems to work well with concurrent fscks, although they still do redundant work due to the commit granularity. Occasionally two writes will conflict, and one is then deferred and happens later. Except, with 3 concurrent fscks, I got failures: git-annex: user error (SQLite3 returned ErrorBusy while attempting to perform prepare "SELECT \"fscked\".\"key\"\nFROM \"fscked\"\nWHERE \"fscked\".\"key\" = ?\n": database is locked) Argh!!!		2015-02-18 15:54:24 -04:00
..
Fsck.hs	use WAL mode to ensure read from db always works, even when it's being written to	2015-02-18 15:54:24 -04:00
Handle.hs	use WAL mode to ensure read from db always works, even when it's being written to	2015-02-18 15:54:24 -04:00
Types.hs	convert incremental fsck to using sqlite database	2015-02-16 15:35:26 -04:00