Skip to content

Instantly share code, notes, and snippets.

@demaniak

demaniak/gist:77a46e079e2cb2977f1fc12b1bd499a1

Created March 25, 2026 09:21
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save demaniak/77a46e079e2cb2977f1fc12b1bd499a1 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save demaniak/77a46e079e2cb2977f1fc12b1bd499a1 to your computer and use it in GitHub Desktop.
Download ZIP
Paperless-ngx, GlusterFS, celery beat NOT compatible with mount option "direct-io-mode=enable"
Raw
gistfile1.txt
As the title states, if you are running your Paperless-ngx instance with GlusterFS provided storage,
do not use the `direct-io-mode=enable` client mount option.
It will result in a permanent error loop where celery will attempt to initialize the scheduling database, and then
error out with a message indicating "device (file) not found". I do not have the *exact* error text available
currenlty, unfortunately,
As [per this resource](https://github.com/vtcifer/glusterfs-sqlite-test), there is a bunch of volume options
that you should set for posix compliance ito locking etc, which is where I initially found the client mount option.
The volume options seem fine to add.
Not sure what the impact is of NOT using `direct-io-mode=enable` as mount option, but so far everything seems fine.
Side note: Jellyfin also does not like that mount option.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment