ENOSPC no space left on device -Nodejs

Question

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

score 162 · Answer 1 · edited Apr 21 '21 at 07:06

162

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

$ docker system prune

Link to official docs

edited Apr 21 '21 at 07:06

Carlos Morales

5,676
4
34
42

answered Aug 29 '19 at 08:09

Renjith

2,025
3
12
20

This also worked for me, do you know why? – Carlos Morales Apr 21 '21 at 07:05
Probably because someone who used your computer or you yourself opened a docker at some point and forgot to close it. Or maybe some app uses a docker and forgot to close it. Whatever the cause is it sure freed a lot of space for me : ) – Trake Vital Jun 01 '21 at 06:07
7

I would suggest using `docker system prune --all` to free even more space – Trake Vital Jun 01 '21 at 06:10
1

This error happens when there's not enough space available on the disk. If you are using Docker and building the containers from the same machine without using the docker hub, then probably the disk becomes eventually full because of the orphan/unused containers the images you have been pulling and building. So this command simply helps us to prune the unused images and containers. Thereby we can free up the space. After we free up the space, the Node.js app will have enough space to run. – Renjith Oct 12 '21 at 04:45

score 53 · Answer 2 · answered Apr 12 '19 at 16:49

53

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

answered Apr 12 '19 at 16:49

Hailin Tan

989
9
7

2

what is -af flag ? – Learner Jan 28 '20 at 09:41
12

a=Remove all unused images not just dangling ones, f=Do not prompt for confirmation – Sovattha Sok Feb 05 '20 at 09:00
-a flag helped. thanks – Stephane Jun 15 '22 at 13:41

omt66 · Answer 3 · 2018-05-09T18:31:07.713

44

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

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

edited May 09 '18 at 18:31

answered May 09 '18 at 17:37

omt66

4,765
1
23
21

3

In Docker based environments, doing this in the host works for all containers. – Yohan Liyanage Apr 18 '19 at 08:20
I'm in a Docker-based environment as well. How exactly do I do this in the host @YohanLiyanage ? – him229 Jun 25 '20 at 18:38
1

What is your -p flag ? it does not exist on macOS – Cyril Duchon-Doris Aug 03 '21 at 09:57
I see this helped a lot of people but it is not helping me. even `df -h` doesn't show any disk utilization of more than 50%. Do I need to restart anything after running this command? – mohit sharma Aug 26 '21 at 13:21
1

What about Windows? – fourk Oct 28 '21 at 18:40

score 14 · Answer 4 · edited Mar 06 '20 at 00:58

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

Hi narasimhanaidu, please remember to enclose your code in backticks (`myVar = 1 + 1`) or with spacing so that it's clear what is description and what is code. — Fons MA, Nov 06 '19 at 07:02

score 5 · Answer 5 · answered Aug 23 '18 at 17:05

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.

score 5 · Answer 6 · answered May 20 '21 at 20:16

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

score 4 · Accepted Answer · answered Jun 20 '18 at 13:45

4

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

answered Jun 20 '18 at 13:45

Yinka

1,741
4
15
23

or just make sure there is space left on your device if you get an error saying "no space left on device" – Phil Mar 09 '21 at 16:05
Yes, this is common mistake developers do, forgot to clear the files from temp after uploading files. Eventually, the disk space becomes full and the machine ran out of space. This also happens when we implemented a logging service and forgot to monitor the disk usage. The logs grow and it leads to the machine ran out of space. So don't forget to "log rotation" when implementing a logging service. – Renjith Oct 12 '21 at 04:53
That's not super helpful without saying where the temp folder is. – hartshoj Aug 20 '23 at 19:49

vipinlalrv · Answer 8 · 2019-07-01T07:00:50.847

4

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

edited Jul 01 '19 at 07:00

answered Jun 27 '19 at 07:02

vipinlalrv

2,975
1
14
9

1

macOS : sysctl: unknown oid 'fs.inotify.max_user_watches' and -p flag does not exist – Cyril Duchon-Doris Aug 03 '21 at 10:59

score 3 · Answer 9 · answered Aug 12 '21 at 13:17

3

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

answered Aug 12 '21 at 13:17

Subhrangshu Adhikary

394
3
10

score 2 · Answer 10 · answered Dec 05 '22 at 21:42

2

This worked for me:

sudo docker system prune -af

answered Dec 05 '22 at 21:42

Awara Amini

307
1
6

Daniel Danielecki · Answer 11 · 2023-01-05T08:23:47.503

1

Open Docker Desktop
Go to Troubleshoot
Click Reset to factory defaults

edited Jan 05 '23 at 08:23

answered Jul 11 '20 at 09:05

Daniel Danielecki

8,508
6
68
94

Thank you Daniel, after spending half of my afternoon on this, you saved me the second half... ps: Even after `sudo docker system prune -af` I still had the error, only this solution worked for me. – olivier dumas Oct 19 '22 at 15:55

score 1 · Answer 12 · answered Sep 04 '20 at 20:13

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

Yes!!! That -df was a huge help! The above answers didn't work for me, at least I have a chance now! Tysm! — Jen, Feb 01 '21 at 22:47

score 1 · Answer 13 · answered Jan 30 '22 at 02:50

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.

score 0 · Answer 14 · answered May 11 '18 at 15:00

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.

Zia Ullah · Answer 15 · 2021-05-09T10:32:03.220

0

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.

edited May 09 '21 at 10:32

answered May 08 '21 at 18:34

Zia Ullah

315
3
11

score 0 · Answer 16 · answered Jun 07 '21 at 02:25

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.

score 0 · Answer 17 · answered Nov 07 '22 at 08:23

I used to check free space first using this command. to show show human-readable output

free -h

then i reclaimed more free space to almost

Total reclaimed space: 2.77GB from 0.94GB using this command

   sudo docker system prune -af

this worked for me.

ENOSPC no space left on device -Nodejs

17 Answers17

tldr;

Restart Docker Desktop