ENOSPC no space left on device -Nodejs

node.js Problem Overview

I just built an application with expressJs for an institution where they upload video tutorials. At first the videos were being uploaded to the same server but later I switched to Amazon. I mean only the videos are being uploaded to Amazon. Now I get this error whenever I try to upload ENOSPC no space left on device. I have cleared the tmp file to no avail.I need to say that I have searched extensively about this issue but none of d solutions seems to work for me

node.js Solutions

Solution 1 - node.js

Just need to clean up the Docker system in order to tackle it. Worked for me.

$ docker system prune

Link to official docs

Solution 2 - node.js

I had the same problem, take a look at the selected answer in the Stackoverflow here:

https://stackoverflow.com/questions/22475849/node-js-error-enospc

Here is the command that I used (my OS: LinuxMint 18.3 Sylvia which is a Ubuntu/Debian based Linux system).

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

Solution 3 - node.js

In my case, I got the error 'npm WARN tar ENOSPC: no space left on device' while running the nodeJS in docker, I just used below command to reclaim space.

sudo docker system prune -af

Solution 4 - node.js

I have come across a similar situation where the disk is free but the system is not able to create new files. I am using forever for running my node app. Forever need to open a file to keep track of node process it's running.

If you’ve got free available storage space on your system but keep getting error messages such as “No space left on device”; you’re likely facing issues with not having sufficient space left in your inode table.

use df -i which gives IUser% like this

Filesystem       Inodes  IUsed    IFree IUse% Mounted on
udev             992637    537   992100    1% /dev
tmpfs            998601   1023   997578    1% /run

If your IUser% reaches 100% means your "inode table" is exhausted

Identify dummy files or unnecessary files in the system and deleted them

Solution 5 - node.js

I got this error when my script was trying to create a new file. It may look like you've got lots of space on the disk, but if you've got millions of tiny files on the disk then you could have used up all the available inodes. Run df -hi to see how many inodes are free.

Solution 6 - node.js

I had the same problem, you can clear the trash if you haven't already, worked for me:

(The command I searched from a forum, so read about it before you decide to use it, I'm a beginner and just copied it, I don't know the full scope of what it does exactly)

$ rm -rf ~/.local/share/Trash/*

The command is from this forum:

https://askubuntu.com/questions/468721/how-can-i-empty-the-trash-using-terminal

Solution 7 - node.js

Well in my own case. What actually happened was while the files were been uploaded on Amazon web service, I wasn't deleting the files from the temp folder. Well every developer knows that when uploading files to a server they are initially stored in the temp folder before being copied to whichever folder you want it to(I know for Nodejs and php); So try and delete your temp folder and see. And ensure ur upload method handles clearing of your temp folder immediately after every upload

Solution 8 - node.js

You can set a new limit temporary with:

sudo sysctl fs.inotify.max_user_watches=524288

sudo sysctl -p

If you like to make your limit permanent, use:

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

sudo sysctl -p

Solution 9 - node.js

Adding to the discussion, the above command works even when the program is not run from Docker.

Repeating that command:

sudo sysctl fs.inotify.max_user_watches=524288
docker system prune

Solution 10 - node.js

The previous answers fixed my problem for a short period of time. I had to do find the big files that weren't being used and were filling my disk. on the host computer I run: df I got this, my problem was: /dev/nvme0n1p3

Filesystem     1K-blocks      Used Available Use% Mounted on
udev            32790508         0  32790508   0% /dev
tmpfs            6563764    239412   6324352   4% /run
/dev/nvme0n1p3 978611404 928877724         0 100% /
tmpfs           32818816    196812  32622004   1% /dev/shm
tmpfs               5120         4      5116   1% /run/lock
tmpfs           32818816         0  32818816   0% /sys/fs/cgroup
/dev/nvme0n1p1    610304     28728    581576   5% /boot/efi
tmpfs            6563764        44   6563720   1% /run/user/1000

I installed ncdu and run it against root directory, you may need to manually delete an small file to make space for ncdu, if that's is not possible, you can use df to find the files manually:

sudo apt-get install ncdu
sudo ncdu /

that helped me to identify the files, in my case those files were in the /tmp folder, then I used this command to delete the ones that weren't used in the last 10 days: With this app I was able to identify the big files and delete tmp files: (Sep-4 12:26)

sudo find /tmp -type f -atime +10 -delete

Solution 11 - node.js

tldr;

Restart Docker Desktop

The only thing that fixed this for me was quitting and restarting Docker Desktop.

I tried docker system prune, removed as many volumes as I could safely do, removed all containers and many images and nothing worked until I quit and restarted Docker Desktop.

Before restarting Docker Desktop the system prune removed 2GB but after restarting it removed 12GB.

So, if you tried to run system prune and it didn't work, try restarting Docker and running the system prune again.

That's what I did and it worked. I can't say I understand why it worked.

Solution 12 - node.js

The issue was actually as a result of temp folder not being cleared after upload, so all the videos that have been uploaded hitherto were still in the temp folder and the memory has been exhausted. The temp folder has been cleared now and everything works fine now.

Solution 13 - node.js

Open `Docker Desktop
Go to 'Troubleshoot'
Click 'Reset to factory defaults`

Solution 14 - node.js

I struggled hard with it, some time, following command worked.

docker system prune

But then I checked the volume and it was full. I inspected and came to know that node_modules have become the real trouble.

So, I deleted node_modules, ran again NPM install and it worked like charm.

Note:- This worked for me for NODEJS and REACTJS project.

Solution 15 - node.js

In my case, Linux ext4 file system, large_dir feature should be enabled.

// check if it's enabled
sudo tune2fs -l /dev/sdc  | grep large_dir

// enable it
sudo tune2fs -O  large_dir  /dev/sda

On Ubuntu, ext4 FS will have a 64M limit on number of files in a single directory by default, unless large_dir is enabled.

Content Type	Original Author	Original Content on Stackoverflow
Question	Yinka	View Question on Stackoverflow
Solution 1 - node.js	Renjith	View Answer on Stackoverflow
Solution 2 - node.js	omt66	View Answer on Stackoverflow
Solution 3 - node.js	Hailin Tan	View Answer on Stackoverflow
Solution 4 - node.js	narasimhanaidu budim	View Answer on Stackoverflow
Solution 5 - node.js	alnorth29	View Answer on Stackoverflow
Solution 6 - node.js	Xelphin	View Answer on Stackoverflow
Solution 7 - node.js	Yinka	View Answer on Stackoverflow
Solution 8 - node.js	vipinlalrv	View Answer on Stackoverflow
Solution 9 - node.js	Subhrangshu Adhikary	View Answer on Stackoverflow
Solution 10 - node.js	Carlos Orduño	View Answer on Stackoverflow
Solution 11 - node.js	Joshua Dyck	View Answer on Stackoverflow
Solution 12 - node.js	Yinka	View Answer on Stackoverflow
Solution 13 - node.js	Daniel Danielecki	View Answer on Stackoverflow
Solution 14 - node.js	Zia Ullah	View Answer on Stackoverflow
Solution 15 - node.js	spikeyang	View Answer on Stackoverflow