Yesterday, 09:47 PM
inotify is the linux system that handles "watching" files for changes. There is a configurable max set in every operating system and while it can be changed, each inotify watcher takes up memory in kernel space. While I have never encountered the error you are mentioning myself, it is possible that jellyfin is making too many inotify watchers for all of the files/folders that you have in your library. If you uncheck the "Enable real time monitoring" for the library you will loose the ability to have jellyfin automatically pick up new media, and require a re-scan every time new media is added or changed, but you will probably stop hitting the inotify max limit.
Otherwise I would google "how to raise inotify limit on <your operating system>". It will probably involve changing a system configuration or boot parameter and then restarting your machine.
I have no idea why this would cause only some clients to break though, I would have assumed it would cause the server to break.
Otherwise I would google "how to raise inotify limit on <your operating system>". It will probably involve changing a system configuration or boot parameter and then restarting your machine.
I have no idea why this would cause only some clients to break though, I would have assumed it would cause the server to break.