From 7ac161395bb20645c080d189aa0609d6422d8f5d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 5 Aug 2022 14:10:47 -0400 Subject: [PATCH] comment --- ...nt_9_d0d441c94af2fe63ed1b20fb031181a3._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_9_d0d441c94af2fe63ed1b20fb031181a3._comment diff --git a/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_9_d0d441c94af2fe63ed1b20fb031181a3._comment b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_9_d0d441c94af2fe63ed1b20fb031181a3._comment new file mode 100644 index 0000000000..d27ad40762 --- /dev/null +++ b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_9_d0d441c94af2fe63ed1b20fb031181a3._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 9""" + date="2022-08-05T18:05:45Z" + content=""" +@yoh Mounting the cifs filesystem with nobrl should avoid the problem. +To make that safe, you *also* need to set annex.pidlock. + +Setting annex.pidlock on its own will not help. + +I don't think that git-annex can be changed in any way that makes sqlite +work on this filesystem in its default state. What I discussed in comment +#7 seems like the only feasible improvement to git-annex and would only +help the user learn about the mount option. +"""]]