mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

comment

Browse source
This commit is contained in:
Joey Hess 2019-09-26 13:04:50 -04:00
parent db1fb97699
commit 06e57449a9
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 22 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_5_bc9b8c1b80a3308c997fdccbf8465f08._comment Normal file
View file

@ -0,0 +1,22 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2019-09-26T16:47:02Z"
content="""
I've found several discussions about Sqlite on CIFS.
https://stackoverflow.com/questions/42722855/sqlite-3-on-windows-share-cifs-access-from-ubuntu-nobrl-risk
That also had all write actions fail with "locked".
It suggests mounting the CIFS filesystem with the "nobrl" mount option.
Another thread suggested instead the "nolock" mount option.
Those may be worth trying, although I'd make sure that
1. annex.pidlock is set to true in the repository's git config.
As long as it is, disabling locking at the database level is not unsafe,
since only one git-annex process will be able to use the database.
2. You only ever use git-annex on one computer at a time in a given
repository on this CIFS drive.
"""]]