Skip to content
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

fs watch error: ENOSPC syscall watch (linux) #74

Open
ob7 opened this issue Apr 27, 2015 · 0 comments
Open

fs watch error: ENOSPC syscall watch (linux) #74

ob7 opened this issue Apr 27, 2015 · 0 comments

Comments

@ob7
Copy link

ob7 commented Apr 27, 2015

I had takana working fine for a while...now out of NOWHERE it won't save to the scratch directory, and therefor no updates are pushed to the browser (because theres no file to push)

A little research led me to this:

ENOSPC means error no space, some people said that means there is no space on disk to write too, but in this case it actually means theres no more watches available...it has to do with the kernel, if you use the following parameter inside sysctl to set it, there is no more ENOSPC fs watch errors, as the kernel will now do its thing like it should.

sysctl fs.inotify.max_user_watches=524288

sources:
http://stackoverflow.com/questions/16748737/grunt-watch-error-waiting-fatal-error-watch-enospc
https://groups.google.com/forum/#!topic/nodejs/LX7sz9f-fmY
http://linux.die.net/man/2/inotify_add_watch
https://wiki.archlinux.org/index.php/Sysctl

I understand if the repo owner doesn't respond to these issues, because they are really issues with how npm works not takana.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant