comment
authorJoey Hess <joeyh@joeyh.name>
Fri, 5 Aug 2022 18:10:47 +0000 (14:10 -0400)
committerJoey Hess <joeyh@joeyh.name>
Fri, 5 Aug 2022 18:10:47 +0000 (14:10 -0400)
doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_9_d0d441c94af2fe63ed1b20fb031181a3._comment [new file with mode: 0644]

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 (file)
index 0000000..d27ad40
--- /dev/null
@@ -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.
+"""]]