No Space Left on Device

No space left on device

Such difference between the output of du -sh and df -h may happen if some large file has been deleted, but is still opened by some process. Check with the command lsof | grep deleted to see which processes have opened descriptors to deleted files. You can restart the process and the space will be freed.

error: file write error: No space left on device

It depends on where you are trying to do the git add .

As mentioned here:

The /snap mounts come from using software packages installed with Snap.

These utilize loop devices and are usually not writable.

You will get some sort of "No space on device" error when trying to write to any of these locations and that is represented in df -h as showing those mounts as 100% in use.

But in your case, assuming the repository is in /dev/...:

devfs                 392       392         0   100%     679          0  100%   /dev

That means you don't have enough inodes.

Look for files to delete:

for x in /* ; do echo $x ; find $x | wc -l ; done

The goal is to free inode usage or increase the number of inodes.

ENOSPC no space left on device -Nodejs

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

Docker-compose - no space left on device

Increase your disk size for docker. Check your status with docker system df Also you can clean your volumes with prune docker system prune --volumes

---

Related Topics