3 avatar="http://cdn.libravatar.org/avatar/d7f0d33c51583bbd8578e4f1f9f8cf4b"
5 date="2019-09-26T20:39:41Z"
7 The lock issue seems confirmed here. And the \"nobrl\" mount option solves the issue.
9 Maybe you should inform the user about \"nobrl\" & \"annex.pidlock\" during the \"git annex init\" filesystem check, refuse to go on and propose legacy direct mode instead if user cannot accept to have no filesystem locking ?
11 Without changing my mount options:
13 SQLite version 3.27.2 2019-02-25 16:06:06
14 Enter \".help\" for usage hints.
15 sqlite> PRAGMA journal_mode=WAL;
16 Error: database is locked
17 sqlite> create table foo (name varchar);
18 Error: database is locked
19 sqlite> insert into foo (name) values (\"joey\");
20 Error: no such table: foo
23 After adding \"nobrl\" in the mount options:
25 SQLite version 3.27.2 2019-02-25 16:06:06
26 Enter \".help\" for usage hints.
27 sqlite> PRAGMA journal_mode=WAL;
29 sqlite> create table foo (name varchar);
30 sqlite> insert into foo (name) values (\"joey\");
33 It seems \"nolock\" is an alias for \"nobrl\", results are the same; when I put \"nolock\" in the mount options, I end up with \"nobrl\" in the \"mount\" command output.
35 Finally, with the \"nobrl\" mount option:
37 $ cd /media/mydisk/tmp/
40 Dépôt Git vide initialisé dans /media/mydisk/tmp/.git/
43 Detected a filesystem without fifo support.
45 Disabling ssh connection caching.
47 Detected a crippled filesystem.
49 Entering an adjusted branch where files are unlocked as this filesystem does not support locked files.
51 Basculement sur la branche 'adjusted/master(unlocked)'
53 (recording state in git...)
56 (recording state in git...)