-
-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same issue as #99 - inotify no space left on device #152
Comments
How many objects do you have in that dir? FWIW, I have set inotify as high as 10 million without issue. So as a test, you can try bumping it up really high to see if the error clears, then lowering in increments. The one thing I'm not sure of is if the container needs restarted after updating inotify setting on the host, I think it does but I'm not 100% on that. |
Not many objects at all, we would be talking like maybe 100 files, if that. i also tried with higher than 524288 but it made no difference, ofcourse restarting the container after the tests. Everything other than inotify works fine :) |
So it seems i had multiple fs.inotify.max_user_watches lines in my sysctl, fixed :) |
how do you change sysctl such that it's not lost when recreating the container? EDIT: Nevermind, found out that its carried over automatically from the host system. |
I'm having the same issue as #99 but with a local mount and i have set the max watches as a extreme test to 524288
Mar 16 21:11:42 ERR Failed initialising jobs error="watch directory: /mnt/local/Media: no space left on device" trigger=inotify
FWIW i'm running the docker container, not sure if that matters?
The text was updated successfully, but these errors were encountered: