To avoid this error, we need to increase the inotify watcher limit.
The way to do this is different on Arch based distributions than other Linux distributions.
Check for an already existing inotify config file (recent versions of Manjaro include one)
ls /etc/sysctl.d/*-max_user_watches.confecho fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max_user_watches.conf && sudo sysctl --system(in the rare case where it outputs multiple files, continue using the last one in the list)
# replace `/etc/sysctl.d/50-max_user_watches.conf` with the file returned from the previous `ls` command
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/50-max_user_watches.conf && sudo sysctl --systemcat /proc/sys/fs/inotify/max_user_watchesExpected output: 524288
OK thanks for the reply. The two events were associated by temporal locality. I received the notification from VS Code ~30 s after applying the
fstabchange & remount. Thus my human brain decided that the two events were associated in a causal relationship.Not surprised- I ended up reverting the "optimizations" to
fstabnot very long after I made them. The volume in question (mounted as/) is a RAID 10 of 4 x Samsung 970 Evo SSDs. Which is what prompted her to recommend those settings.