blocks|key|2963131|text|ENOSPC表示驱动器上没有空间。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2963132|也许/tmp已经满了？您可以通过设置npm+config+set+tmp+/path/to/some/other/dir将npm配置为使用不同的临时文件夹，也可以删除/tmp文件夹中的所有内容。|2963133|来源:+github中npm的repo中的npm+1.1.21+cannot+write,+ENOSPC。|2963134|注意，我用上述源代码中描述的方式解决了我的问题。但是，请参阅更全面的Murali+Krishna's+answer。|2963135|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/npm/npm/issues/2461|1|https://stackoverflow.com/a/32600959/2385565^0|0|6|0|2|4|I|16|1P|3|2B|4|0|L|V|0|0|Y|N|1|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]|$9|13|A|14|B|C]|$9|15|A|16|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|J|3|K|5|6|7|1B|8|@]|D|@$9|1C|A|1D|1|1E]]|E|$]]|$1|L|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|M|$N|$5|O|P|Q|E|$R|S]]|T|$5|O|P|Q|E|$R|U]]]]

<code>ENOSPC</code> means that there is no space on the drive.
Perhaps <code>/tmp</code> is full? You can configure <code>npm</code> to use a different temp folder by setting <code>npm config set tmp /path/to/some/other/dir</code>, or maybe delete everything out of the <code>/tmp</code> folder.
Source: <a href="https://github.com/npm/npm/issues/2461" rel="noreferrer">npm 1.1.21 cannot write, ENOSPC</a> in npm's repo in github.
Note I solved my problem in the way that described in above source. However, see <a href="https://stackoverflow.com/a/32600959/2385565">Murali Krishna's answer</a>, which is more comprehensive.

blocks|key|159450|text|如果您在linux文件系统上的/tmp挂载被挂载为溢出(通常大小为1MB)，这可能是因为您没有指定/tmp作为其自己的分区，并且您的根文件系统已被填满，而/tmp被重新挂载为备用分区。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|159451|要在清除空间后修复此问题，只需卸载回退，它应在其原始点重新挂载：|159452|sudo+umount+overflow|code-block|syntax|javascript|159453|entityMap^0|F|4|1D|4|25|4|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

If your <code>/tmp</code> mount on a linux filesystem is mounted as overflow (often sized at 1MB), this is likely due to you not specifying <code>/tmp</code> as its own partition and your root filesystem filled up and <code>/tmp</code> was remounted as a fallback.

To fix this after you’ve cleared space, just unmount the fallback and it should remount at its original point:

<pre><code>sudo umount overflow
</code></pre>

blocks|key|2750689|text|在我的例子中，在linux上，sudoing解决了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750690|示例：|2750691|sudo+gulp+dev|code-block|syntax|javascript|2750692|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my case, on linux, sudoing fixed the problem.

Example:

<pre><code>sudo gulp dev
</code></pre>

blocks|key|2963192|text|运行以下命令以避免ENOSPC：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2963193|echo+fs.inotify.max_user_watches=524288+%7C+sudo+tee+-a+/etc/sysctl.conf+&&+sudo+sysctl+-p|code-block|syntax|javascript|2963194|2963195|对于Arch+Linux，将此行添加到/etc/sysctl.d/99-sysctl.conf|offset|length|style|CODE|2963196|fs.inotify.max_user_watches=524288|2963197|然后执行：|2963198|sysctl+--system|2963199|这也将在重新启动后保持不变。Technical+Details+Source|2963200|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details^0|0|0|0|J|S|0|0|0|0|E|O|0|0^^$0|@$1|2|3|4|5|6|7|13|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|14|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@$J|17|K|18|L|M]]|9|@]|A|$]]|$1|N|3|O|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|P|3|Q|5|6|7|1A|8|@]|9|@]|A|$]]|$1|R|3|S|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|T|3|U|5|6|7|1C|8|@]|9|@$J|1D|K|1E|1|1F]]|A|$]]|$1|V|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|W|$X|$5|Y|Z|10|A|$11|12]]]]

Run the below command to avoid ENOSPC:

<pre><code>echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf &amp;&amp; sudo sysctl -p
</code></pre>

<hr>

For Arch Linux add this line to <code>/etc/sysctl.d/99-sysctl.conf</code>:

<pre><code>fs.inotify.max_user_watches=524288
</code></pre>

Then execute:

<pre><code>sysctl --system
</code></pre>

This will also persist across reboots.
<a href="https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers#the-technical-details" rel="noreferrer">Technical Details Source</a>

blocks|key|159458|text|这不能归功于此，但@grenade指出，npm+dedupe会解决问题(文件太多)，而不是症状。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|159459|来源：Grunt+watch+error+-+Waiting…Fatal+error:+watch+ENOSPC。|159460|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/users/68115/grenade|1|https://stackoverflow.com/a/31926452/518191^0|K|A|9|8|0|0|3|1H|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@$9|U|A|V|1|W]]|E|$]]|$1|F|3|G|5|6|7|X|8|@]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

Can't take credit for this, but <a href="https://stackoverflow.com/users/68115/grenade">@grenade</a> pointed out that <code>npm dedupe</code> will fix the cause (too many files) and not the symptom. 

Source: <a href="https://stackoverflow.com/a/31926452/518191">Grunt watch error - Waiting…Fatal error: watch ENOSPC</a>.

blocks|key|161856|text|我解决了杀死所有跟踪器控制进程的问题(如果你使用GDM，你可以尝试，如果脚本在服务器上运行，显然不是你的情况)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|161857|tracker-control+-r|code-block|syntax|javascript|161858|我的设置:+Arch+with+GNOME+3|161859|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I solved my problem killing all tracker-control processes (you could try if you use GDM, obviously not your case if the script is running on a server)

<pre><code>tracker-control -r
</code></pre>

My setup: Arch with GNOME 3

blocks|key|159464|text|对我来说，我已经达到了一个用户可以拥有的最大文件数|type|unstyled|depth|inlineStyleRanges|entityRanges|data|159465|使用quota+-s检查您的数字，并确保文件下的数量不是太接近配额|offset|length|style|CODE|159466|entityMap^0|0|2|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

For me I had reached the maximum numbers of files a user can own

Check your numbers with <code>quota -s</code> and that the number under files is not too close to the quota

blocks|key|2963224|text|如果您在尝试运行ember+server命令时遇到此错误，请使用rm+-rf+tmp目录。然后再次运行ember+s。这对我有帮助。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2963225|entityMap^0|8|C|W|A|1F|7|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

If you encounter this error during trying to run <code>ember server</code> command please <code>rm -rf tmp</code> directory. Then run <code>ember s</code> again. It helped me.

blocks|key|2750740|text|重新启动机器为我解决了这个问题。我首先尝试擦除/tmp/，但node仍在抱怨。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2750741|entityMap^0|N|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Rebooting the machine solved the problem for me. I first tried wiping <code>/tmp/</code> but node was still complaining.

blocks|key|2963240|text|解决我问题的一个简单方法是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2963241|npm+cache+clear|code-block|syntax|javascript|2963242|npm或由其控制的进程正在查看太多文件。在build节点上更新max_user_watches可以永远修复它。对于debian，将以下内容放在终端上：|offset|length|style|BOLD|2963243|echo+fs.inotify.max_user_watches=524288+%7C+sudo+tee+-a+/etc/sysctl.conf+&&+sudo+sysctl+-p|2963244|如果你想知道Increase+the+amount+of+inotify+watchers是怎么做到的，只需要点击链接。|2963245|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers^0|0|0|0|3|0|0|6|13|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@]|9|@$I|15|J|16|1|17]]|A|$]]|$1|Q|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

A simple way that solve my problem was:

<pre><code>npm cache clear
</code></pre>

npm or a process controlled by it is watching too many files. Updating max_user_watches on the build node can fix it forever. For debian put the following on terminal:

<pre><code>echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf &amp;&amp; sudo sysctl -p
</code></pre>

If you want know how <a href="https://github.com/guard/listen/wiki/Increasing-the-amount-of-inotify-watchers" rel="noreferrer">Increase the amount of inotify watchers</a> only click on link.

blocks|key|2750774|text|我也犯了同样的错误。当我运行Reactjs应用程序时。我所要做的就是删除node_modules文件夹，然后再次输入并安装node_modules。这样就消除了错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750775|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I was having Same error. While I run Reactjs app. What I do is just remove the node_modules folder and type and install node_modules again. This remove the error.

blocks|key|160732|text|在Ubuntu+18.04上，我尝试了一个通过it+/node重新激活文件监视的技巧，它在这里也有效。对于那些没有权限访问系统配置文件的人来说，这可能很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160733|CHOKIDAR_USEPOLLING=1+npm+start|code-block|syntax|javascript|160734|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

On Ubuntu 18.04 , I tried a trick that I used to reactivate the file watching by ionic/node, and it works also here. This could be useful for those who don't have access to system conf files.

<pre><code>CHOKIDAR_USEPOLLING=1 npm start
</code></pre>

blocks|key|2750806|text|这听起来很奇怪，但是的，系统重新启动或killall+node为我解决了这个问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2750807|entityMap^0|J|C|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This sounds very odd, but yes, a system reboot or <code>killall node</code> solves the problem for me.

blocks|key|2963323|text|在Linux上，这可能是对文件监视数量的限制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2963324|开发服务器使用inotify实现热重载。inotify+API允许开发服务器监视文件，并在文件发生更改时得到通知。|offset|length|2963325|默认的inotify文件监视限制因发行版而异(在Fedora上为8192)。开发服务器的需求经常超过此限制。|2963326|最好的方法是尝试临时增加文件监视限制，然后如果您对此满意，则将其设置为永久配置更改。但请注意，这会更改整个系统的配置，而不仅仅是节点。|2963327|要查看当前限制，请执行以下操作：|2963328|sysctl+fs.inotify.max_user_watches|code-block|syntax|javascript|2963329|要临时设置新限制，请执行以下操作：|2963330|#+this+limit+will+revert+after+reset
sudo+sysctl+fs.inotify.max_user_watches=524288
sudo+sysctl+-p
#+now+restart+the+server+and+see+if+it+works|2963331|设置永久限制的步骤：|2963332|echo+fs.inotify.max_user_watches=524288+%7C+sudo+tee+-a+/etc/sysctl.conf
sudo+sysctl+-p|2963333|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Inotify^0|0|7|7|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|F|3|G|5|6|7|1B|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1D|8|@]|9|@]|A|$]]|$1|L|3|M|5|N|7|1E|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|1F|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|1G|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|1H|8|@]|9|@]|A|$]]|$1|W|3|X|5|N|7|1I|8|@]|9|@]|A|$O|P]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

On Linux, this is likely to be a limit on the number of file watches.

The development server uses <a href="https://en.wikipedia.org/wiki/Inotify" rel="noreferrer">inotify</a> to implement hot-reloading. The inotify API allows the development server to watch files and be notified when they change.

The default inotify file watch limit varies from distribution to distribution (8192 on Fedora). The needs of the development server often exceeds this limit.

The best approach is to try increasing the file watch limit temporarily, then making that a permanent configuration change if you're happy with it. Note, though, that this changes your entire system's configuration, not just node.

To view your current limit:

<pre><code>sysctl fs.inotify.max_user_watches
</code></pre>

To temporarily set a new limit:

<pre><code># this limit will revert after reset
sudo sysctl fs.inotify.max_user_watches=524288
sudo sysctl -p
# now restart the server and see if it works
</code></pre>

To set a permanent limit:

<pre><code>echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
</code></pre>

blocks|key|2750830|text|如果您使用的是VS+Code，那么它应该无法在大型工作区中查看错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2750831|"Visual+Studio+Code+is+unable+to+watch+for+file+changes+in+this+large+workspace"+(error+ENOSPC)|code-block|syntax|javascript|2750832|它表明VS代码文件观察器正在耗尽句柄，因为工作区很大且包含许多文件。可以通过运行以下命令来查看当前限制：|2750833|cat+/proc/sys/fs/inotify/max_user_watches|2750834|通过编辑/etc/sysctl.conf并将以下行添加到文件末尾，可以将限制增加到其最大值：|offset|length|style|CODE|2750835|fs.inotify.max_user_watches=524288|2750836|然后，可以通过运行sudo+sysctl+-p来加载新值。|2750837|注意:+524288是观看文件的最大值。虽然你可以观看任何数量的文件，但也建议只观看该限制。|2750838|entityMap^0|0|0|0|0|4|G|0|0|9|E|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@$M|13|N|14|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|16|8|@$M|17|N|18|O|P]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

If you're using VS Code then it'll should unable to watch in large workspace error. 
<pre><code>&quot;Visual Studio Code is unable to watch for file changes in this large workspace&quot; (error ENOSPC)
</code></pre>
It indicates that the VS Code file watcher is running out of handles because the workspace is large and contains many files. The current limit can be viewed by running:
<pre><code>cat /proc/sys/fs/inotify/max_user_watches
</code></pre>
The limit can be increased to its maximum by editing <code>/etc/sysctl.conf</code> and adding this line to the end of the file:
<pre><code>fs.inotify.max_user_watches=524288
</code></pre>
The new value can then be loaded in by running <code>sudo sysctl -p</code>. 
Note: 524288 is the max value to watch the files. Though you can watch any no of files but is also recommended to watch upto that limit only.

blocks|key|2963345|text|它表明VS代码文件观察器正在耗尽句柄，因为工作区很大且包含许多文件。已达到手表的最大限制，您可以通过运行以下命令查看限制：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2963346|cat+/proc/sys/fs/inotify/max_user_watches|code-block|syntax|javascript|2963347|运行下面的代码解决此问题：|2963348|fs.inotify.max_user_watches=524288|2963349|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

It indicates that the VS Code file watcher is running out of handles because the workspace is large and contains many files. The max limit of watches has been reacherd, you can viewed the limit by running:
<pre><code>cat /proc/sys/fs/inotify/max_user_watches
</code></pre>
run below code resolve this issue:
<pre><code>fs.inotify.max_user_watches=524288
</code></pre>

blocks|key|2963368|text|尝试了上面建议的大多数方法。最后，删除node_modules目录对我有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2963369|所以我认为起作用的是：|2963370|2963371|echo+fs.inotify.max_user_watches=524288+%7C+sudo+tee+-a+/etc/sysctl.conf+&&+sudo+sysctl+-p|ordered-list-item|offset|length|style|CODE|2963372|sudo+sysctl+--system|2963373|rm+-r+/tmp*+(!！确保这不会破坏you)|2963374|rm+-r+node_modules|2963375|Restart+system|2963376|的任何功能|2963377|entityMap^0|0|0|0|0|2G|0|0|K|0|0|B|0|0|I|0|0|E|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|10|8|@$H|11|I|12|J|K]]|9|@]|A|$]]|$1|L|3|M|5|G|7|13|8|@$H|14|I|15|J|K]]|9|@]|A|$]]|$1|N|3|O|5|G|7|16|8|@$H|17|I|18|J|K]]|9|@]|A|$]]|$1|P|3|Q|5|G|7|19|8|@$H|1A|I|1B|J|K]]|9|@]|A|$]]|$1|R|3|S|5|G|7|1C|8|@$H|1D|I|1E|J|K]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1F|8|@]|9|@]|A|$]]|$1|V|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|W|$]]

Tried most of the things suggested above. At the end deleting node_modules directory helped me.
So I think what worked is:
<ol>
<li><code>echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf &amp;&amp; sudo sysctl -p</code></li>
<li><code>sudo sysctl --system</code></li>
<li><code>rm -r /tmp*</code> (!! make sure this will not break anything for you)</li>
<li><code>rm -r node_modules</code></li>
<li><code>Restart system</code></li>
</ol>

blocks|key|160797|text|在我的例子中，我这样做了|type|unstyled|depth|inlineStyleRanges|entityRanges|data|160798|yarn+cache+clean

npm+cache+verify

rm+-rf+node_modules/

yarn+install|code-block|syntax|javascript|160799|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In my case, I did this
<pre><code>yarn cache clean

npm cache verify

rm -rf node_modules/

yarn install
</code></pre>

I have a problem with Node.js and uploading files to server. For uploading files to server I use this <a href="https://github.com/Valums-File-Uploader/file-uploader" rel="noreferrer">plugin</a>. When starting file upload to the server, Node.js process crashed and show error:

<blockquote>
 Error: ENOSPC.
</blockquote>

The server code doesn't run.

<pre><code>$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/xvda1 7.9G 4.1G 3.5G 55% /
udev 288M 8.0K 288M 1% /dev
tmpfs 119M 168K 118M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 296M 0 296M 0% /run/shm
/dev/xvdf 9.9G 3.0G 6.5G 32% /vol
overflow 1.0M 1.0M 0 100% /tmp
</code></pre>

Node.js: what is ENOSPC error and how to solve?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我有一个关于Node.js和上传文件到服务器的问题。为了将文件上传到服务器，我使用这个。开始将文件上载到服务器时，Node.js进程崩溃并显示错误：错误: ENOSPC.服务器代码不能运行。$ df -hFilesystem      Size  Used Avail Use% Mounted on/dev/xvda1...

问Node.js:什么是ENOSPC错误，如何解决？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Node.js:什么是ENOSPC错误，如何解决？EN