It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Alright I restarted the computer, and now everything works fine again.

I solved this way
https://code.visualstudio.com/docs/setup/linux
"Visual Studio Code is unable to watch for file changes in this large workspace" (error ENOSPC)#

cat /proc/sys/fs/inotify/max_user_watches

fs.inotify.max_user_watches=524288

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thank you very much!!!

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

it saved my day

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

I ran this line of code in a react-app and everything went back to normal again, thanks!!

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thanks. it's really helpfull

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Thanks man , you are a hero

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Give me the error:
sysctl: illegal option -- p

Using on MacOS

Serve your app as root.....It's work!

Serve your app as root.....It's work!

Could you explain ?

Run sudo npm run serve inside you app folder or run this commands as below:

• su
• enter your password
• npm run serve

Noooooooo don't run your app as root! 💀 🚨 That can cause all kinds of security problems!

What if I deploy to netlify and encounter that error when netlify tries to build the app? On local it's fine

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

Yes It is working

I'm getting this error on Netlify.
Anyone know how to fix it?

I got it today too and did a "clear cache and redeploy" and it worked.

echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
worked

worked too. thanks

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Works for me. Thank you :D

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Thanks mate, it saved my day!

It’s hitting your system's file watchers limit
Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thank you very much!!!

There is a shortcut to setting this parameter. This accomplishes the same thing as the top voted answer:

sudo sysctl fs.inotify.max_user_watches=524288

Thanks smac.. u guys rock

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Worked for me, thank so much!

Error: ENOSPC: System limit for number of file watchers reached,

I am having this issue

Tried echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p but didn't work for me.

Using the sysctl -p approach after setting fs.inotify.max_user_watches did not work for me , either. (by the way this setting was already set to a high value, likely from me trying to fix this issue a while back ago).

The best solution to the problem I found here:

1. Use this script to identify which processes are requiring the most file watchers in your session.
2. You can then query the current max_user_watches value with sysctl fs.inotify.{max_queued_events,max_user_instances,max_user_watches} and then set it to a different value (a lower value may do it)
   sudo sysctl -w fs.inotify.max_user_watches=16384
3. Or you can simply kill the process you found in (1) that consumes the most file watchers (in my case, baloo_file)
4. The above, however, will likely need to be done again when restarting the system - the process we identified as responsible for taking much of the file watchers will (in my case - baloo_file) - will again so the same in the next boot. So to permanently fix the issue - either disable or remove this service/package. I disabled it: balooctl disable.

Now run sudo code --user-data-dir and it should open vscode with admin privileges this time. (by the way when it does not run sudo code --user-data-dir --verbose to see what the problem is - that's how I figured out it had to do with file watchers limit).

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Its working

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

Worked for me, Linux OS

Alternative solution for vscode:

Instead of increasing limits you could also add public and .cache folders to files.watcherExclude

"files.watcherExclude": {
    "**/public/**": true,
    "**/.cache/**": true
}

or

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc

This is the actual solution in my case. It turned out that my watcher exclude pattern had an error. It excluded **/node_modules/*/** instead of **/node_modules/**.

Increasing the system's fs.inotify.max_user_watches only helped counter the symptoms of this error, and didn't help any more when even more folders were added to node_modules.

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Link does not look right.

via https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Link does not look right.

I just quote-replied and referenced an answer higher up in the conversation.

I'm running into this issue on Google Kubernetes Engine (GKE) because you don't appear to have the ability to increase the default fs.inotify.max_user_watches.

Please stop telling people to increase the user watches to such a ridiculously high number. The default value is 8192 for a reason. Each watch consumes 1080 bytes of kernel memory on a 64-bit system. Setting the limit to such a high number would allow EACH USER on the system to potentially allocate number of watches * 1080 bytes of memory.

Tell them to increase the value in small steps until things start to work.

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

thanks mate, you are a hero

If you are getting this error because you are working on a REACT/STRAPI or NODE or something related to javascript and react vis Ubuntu then below will help you.

run this on your terminal

sudo gedit /etc/sysctl.conf

Add a line at the bottom

fs.inotify.max_user_watches=524288

Then save and exit!

sudo sysctl -p

to check it

Then it is solved!

go back to your VS-CODE or any IDE you are using and run your code again

Please stop telling users to set the limit to such a high value (see my previous comment for the reason).

edited

Please stop telling users to set the limit to such a high value (see my previous comment for the reason).

edited now, thanks

@Sugarcothe, I don't understand your new value. Now it's even lower than the default (8192).

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

above command explanation

This command is using the echo command to write the string "fs.inotify.max_user_watches=524288" to a file called "/etc/sysctl.conf" using the tee command with the -a option, which appends the output to the end of the file. The && operator is used to execute the next command sudo sysctl -p, which reloads the sysctl configuration file and sets the new value.
In brief this command will increase the maximum number of inotify watches that can be created by a single user to 524288. This is useful for certain applications that monitor many files and directories, such as text editors and file managers.

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

I've created an issue there to fix that document: guard/listen#568

Restarting my computer fixed the issue.

It’s hitting your system's file watchers limit

Try echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

Read more about what’s happening at https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details

I apologize for my last comment that restarting computer fixes the issue. I got it again, and restarting (a lot) didn't solve. So the shared terminal command is really the correct fixed on the issue. If you're like us, try the terminal command.

Thank you much!