today in work-related fuckery, i have set up a boring-ass linux server running samba, and am attempting to use it as volume storage for our k8s cluster.

[dave@rascalking.com]

today in work-related fuckery, i have set up a boring-ass linux server running samba, and am attempting to use it as volume storage for our k8s cluster.  partly because i'm going to use it as volume storage after i've moved us to docker swarm, and partly because of the clock skew-related issues we had with on-cluster storage.

so, i have done basic "poke it and see if it works" tests, and moved on to running our staging instances against it.  everything is happy except for one service that has this teeny tiny db with no exaggeration a single column a single row in a single table.  we're just storing a string.  which naturally i'm just using sqlite for.  i am getting disk i/o errors trying to open the db.

friends, it turns out that sqlite really super duper does not like running on a smb/cifs share.

[dave@rascalking.com]

so now i get to see if there's a workaround with database options in django or something.  and if not, i get to run down a long list of shitty alternatives and decide the least shitty approach for this, which may very well be a plaintext file on disk and fucking flock().

[dave@rascalking.com]

fine, i'll switch to using nfs.


but i'm not gonna like it.

[tzz@infosec.exchange]

@dave it’s fine. It’s fine. You could do worse than NFS.