-
Notifications
You must be signed in to change notification settings - Fork 59
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
sysctl: fs.inotify.max_user_watches is too low and hard-capped #637
Comments
You might want to check inode counts with |
Maybe we should also consider raising the inotify limits. We currently have:
On my workstation, I have:
Temporary workaround:
|
@dustymabe @travier Provisioning CoreOS with the following bits I don't see this message anymore: - path: /etc/sysctl.d/90-inotify.conf
contents:
inline: |
fs.inotify.max_user_watches = 524288 Can this sysctl value be made default for CoreOS? |
@nrvnrvn how much RAM do you have on that machine (i.e |
@lucab this is how much RAM I have on that machine:
|
@nrvnrvn for context, what is the output of |
@lucab |
Sorry I forgot that I had a custom |
@nrvnrvn @travier thanks both for the feedback.
As observed on a few different VMs:
This does not seem to be specific to FCOS and I'm also seeing it on RHCOS, I've forwarded to RH bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=1888617. |
There is a currently in-progress patch on linux-fsdevel for this, first revision is https://patchwork.kernel.org/project/linux-fsdevel/patch/20201026204418.23197-1-longman@redhat.com/. |
The kernel-side patch for this landed in https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=92890123749bafc317bbfacbe0a62ce08d78efb7 and should be part of 5.11. |
Kernel 5.11 landed in the next stream last week. The fix for this went into next stream release |
The fix for this went into testing stream release |
The fix for this went into stable stream release |
Observing messages like this in system journal:
The text was updated successfully, but these errors were encountered: