[NvimTree] Could not start the fs_event watcher for path /xxxx/xxxx : ENOSPC

[dawaldow]

[NvimTree] Could not start the fs_event watcher for path /xxxx/xxxx : ENOSPC

[gegoune]

Please use steps and minimal configuration as described in https://github.com/nvim-tree/nvim-tree.lua/wiki/Troubleshooting#clean-room-replication. We cannot troubleshoot Nvim configuration distributions.

With that said, are you sure it's not a disk space issue?

[dawaldow]

No disk issues -

I was able to recreate the error/issue in the clean room environment with no changes to the lua file. I attempted to setup the l"og =" information to create a log file, but it doesn't seem to work or I don't know where to put the "log =" information. But with that said...

After reading the clean room link, at the bottom it talked about increasing the number of watchers. I increased fs.inotify.max_user_watches and instances and the error went away. I am not sure how this works, if it just delays the error as the number of watchers is consumed or if it doesn't reach the max (assuming number of files). But I will watch and see how this behaves.

[alex-courtis]

After reading the clean room link, at the bottom it talked about increasing the number of watchers. I increased fs.inotify.max_user_watches and instances and the error went away. I am not sure how this works, if it just delays the error as the number of watchers is consumed or if it doesn't reach the max (assuming number of files). But I will watch and see how this behaves.

That "checks out" although it does not explain ENOSPC at all; you should receive a reasonable message.

Guessing: quemu is using a lot of inotify, maybe OneDrive. Either way, the default limit is very low and needs to be increased by most users. My colleagues and I use intellij which almost immediately saturates inotify, hence we increase it.

[alex-courtis]

I was able to recreate the error/issue in the clean room environment with no changes to the lua file. I attempted to setup the l"og =" information to create a log file, but it doesn't seem to work or I don't know where to put the "log =" information. But with that said...

The log will usually go in ${XDG_STATE_HOME}/nvim/nvim-tree.log. You should receive a startup message that notifies you of this file however there are bugs in nvim 0.9 that squash this; fixed in 0.10.

:mess usually retains and shows it.