On Dec 21, 2017, at 11:40 AM, [email protected] wrote:
>
> [email protected]:fossils on /fossils type fuse.sshfs
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0)
Running SQLite — upon which Fossil is based — over sshfs is a bad idea. The
current implementation doesn’t even try to implement the file locking operation:
https://github.com/libfuse/sshfs/blob/master/sshfs.c#L3304
That structure definition would have to include the “.lock” member for the sort
of locking SQLite does for this to be safe.
See also:
https://www.sqlite.org/howtocorrupt.html#_filesystems_with_broken_or_missing_lock_implementations
There are other network file systems with locking semantics, but it’s often
optional, and when present and enabled, it is often buggy.
Here’s hoping you have some other option. Best would be to store the *.fossils
inside the container. Second best would be to map a [virtual] block device
into the container and put a normal Linux file system on it.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
