From 6d762fafae45cb1f6a6106ac25f347631d6d0ca8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 5 Aug 2022 14:54:10 -0400 Subject: [PATCH] idea --- ..._b96755e44bedf262cbb32403f8edaf0b._comment | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_10_b96755e44bedf262cbb32403f8edaf0b._comment diff --git a/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_10_b96755e44bedf262cbb32403f8edaf0b._comment b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_10_b96755e44bedf262cbb32403f8edaf0b._comment new file mode 100644 index 0000000000..22dddc60bb --- /dev/null +++ b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_10_b96755e44bedf262cbb32403f8edaf0b._comment @@ -0,0 +1,21 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 10""" + date="2022-08-05T18:42:34Z" + content=""" +Another way this could be dealt with is to move the sqlite databases to +a local filesystem. + +Since git-annex only ever uses them for caching information from git, it +can rebuild them, so even a tempfs would work. And it would also be ok if +two git-annex processes accessing the same repo used different sqlite +databases, since they would both build up the same information. +(Even if they were on different computers using a network filesystem.) + +This could be done with a git config. And perhaps get `git-annex init` +to somehow probe for this problem and set the git config. Although, what +path would it set it to? + +(Note that gitAnnexKeysDbIndexCache would also need to be moved since it +contains information about the content of a sqlite database.) +"""]] -- 2.30.2